Method and system for routing messages and connecting users associated with live-connected content

ABSTRACT

According to one embodiment, a first request of a first user is received for communicating with an agent concerning a content item of a media presentation presented to the first user. In response, agents associated with the content identifier are identified. Status of the identified agents is determined. Agent identifiers are transmitted to the second server, the agent identifiers identifying one or more available agents, including a geographic location of the agents. A second request is received from a first user device of the first user, including an agent identifier identifying a first agent selected by the first user from the list and contact information of the first user. In response, a first message is transmitted to a first agent device of the first agent, the first message including the content identifier identifying the content item and the contact information of the first user.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 61/895,963, filed Oct. 25, 2013 and U.S. ProvisionalPatent Application No. 62/014,434, filed Jun. 19, 2014. The disclosureof the above provisional applications is incorporated by referenceherein in its entirety.

FIELD OF THE INVENTION

Embodiments of the present invention relate generally to contentdistribution. More particularly, embodiments of the invention relate torouting messages of the live connected content.

BACKGROUND

In online advertising, internet users are presented with advertisementsas they browse the internet using a web browser. Online advertising isan efficient way for advertisers to convey advertising information topotential purchasers of goods and services. It is also an efficient toolfor organizations such as non-profits and political organizations toincrease their awareness in a target group of people. Ad (advertisement)serving describes the technology and service that places advertisementson web sites. Ad serving technology companies provide software and/orservices to web sites and advertisers to serve ads, count them, choosethe ads that will make the website the most money or the advertiser thebest return, and monitor progress of different advertising campaigns. Adservers come in two flavors: local ad servers and third-party or remotead servers. Local ad servers are typically run by a single publisher andserve ads to that publisher's domains, allowing fine-grained creative,formatting, and content control by that publisher. Remote ad servers canserve ads across domains owned by multiple publishers. They deliver theads from one central source so that advertisers and publishers can trackthe distribution of their online advertisements, and have one locationfor controlling the rotation and distribution of their advertisementsacross the Web.

Most of the conventional Ads are static in which certain informationwill be displayed and in some cases includes contact information of theservice provider who is advertising. However, a viewer of this ad is notable to know whether the services described in an Ad can be provided ina time relevant way (i.e., within the hour, within the day). Today, forexample, if one looks for a local orthodontist surgeon, one would type“local orthodontist surgeon” in for a search field of a browser. Thesearch engine (e.g., Yahoo®) would come back with a list of orthodontistbusinesses that prescribe to this ads type. Depending upon the browser,a phone number of the business may or may not be clickable to establishthe phone contact. If a user is using a Chrome™ browser, and if he/shehas installed the Google Voice™ plugin of the case, then one can clickthe hyperlink, the Google Voice™ plugin will verify the phone numberthat the user would like to call, then initiate the dial for the user.The user will then be connected to the end point of that phone number—inthis case it would likely be the orthodontist office receptionistassuming that person is available. If the user is using a Safari™browser, the user will also be presented with a phone number, which theuser can text to its iPhone using iMessage™. Once the user has receivedthe text, you can dial the orthodontist office from the iPhone andconduct a conversation assuming there is someone who is able to answerthe phone on the orthodontist's end. Although sometimes a map is alsopresented, however, the map is only related to static information suchas an address associated with the Ad. It does not provide anythingregarding the location of the service provider.

Such a limitation is sometimes unacceptable and problematic to some Advisitors and/or providers. A visitor would not know whether there isactually a person or support person available and nearby. Similarly, anAd will run regardless whether there is actually a person or supportperson available. The lack of a live, time-relevant, connection with anAd provider may discourage a visitor from interacting with an Ad toinquire further information.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example and notlimitation in the figures of the accompanying drawings in which likereferences indicate similar elements.

FIG. 1 is a block diagram illustrating a network system providing liveconnect services according to one embodiment of the invention.

FIG. 2 is a block diagram illustrating a system providing live connectservices according to one embodiment of the invention.

FIGS. 3A-3B are block diagrams illustrating a network system providinglive connect services according to some embodiments of the invention.

FIG. 4 is a block diagram illustrating an example of a live connectsystem for providing live connect services according to one embodimentof the invention.

FIG. 5 is a block diagram illustrating a data structure to be used withone embodiment of the invention.

FIG. 6 is a block diagram illustrating a data structure to be used withanother embodiment of the invention.

FIGS. 7A-7B are block diagrams illustrating examples of data structuresaccording to some embodiments of the invention.

FIG. 8 is a block diagram illustrating an example of a live contentserver according to one embodiment of the invention.

FIG. 9 is a block diagram illustrating an example of a data structureaccording to another embodiment of the invention.

FIGS. 10-12 are process diagrams illustrating sample transactions toestablish communication links for live connect Ads according to someembodiments of the invention.

FIGS. 13-14 are flow diagrams illustrating a method for providing liveconnect services according to certain embodiments of the invention.

FIGS. 15A-15C are screenshots illustrating an example of a graphicaluser interface for providing live content according to some embodimentsof the invention.

FIGS. 16A-16J are screenshots illustrating an example of graphical userinterfaces of a mobile application utilized by a specialist according tosome embodiments of the invention.

FIGS. 17-18 are process diagrams illustrating interactions between thelive connect server and a client application of a specialist accordingto some embodiments of the invention.

FIGS. 19A-19H are screenshots illustrating an example of a managementuser interface for managing a business and its users according to oneembodiment of the invention.

FIG. 20 is a processing flow diagram illustrating an example ofadministrative processes according to one embodiments of the invention.

FIG. 21 is a block diagram illustrating a system for providing supportservices to products according to one embodiment of the invention.

FIG. 22 is a block diagram illustrating an example of a support servicesystem of a service center according to one embodiment of the invention.

DETAILED DESCRIPTION

Various embodiments and aspects of the inventions will be described withreference to details discussed below, and the accompanying drawings willillustrate the various embodiments. The following description anddrawings are illustrative of the invention and are not to be construedas limiting the invention. Numerous specific details are described toprovide a thorough understanding of various embodiments of the presentinvention. However, in certain instances, well-known or conventionaldetails are not described in order to provide a concise discussion ofembodiments of the present inventions.

Reference in the specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin conjunction with the embodiment can be included in at least oneembodiment of the invention. The appearances of the phrase “in oneembodiment” in various places in the specification do not necessarilyall refer to the same embodiment.

According to some embodiments, a live connect system is utilized tocoordinate with content providers and content distribution systems toprovide and distribute live content (also simply referred to as liveconnect content) to end users as visitors. With the live connect system,an end user (e.g., visitor) who accesses live content can establish alive communication session with another user (e.g., support agent,specialist) that is associated with the live content at the point intime, for example, for the purpose of discussing further detailedinformation concerning the content presented. The live content presentedto the visitor includes information indicating that there is a supportagent who is available at the point in time to have a live conversationwith the visitor. The live content also includes information indicatinga geographic location of that support agent with respect to thegeographic location of the visitor (e.g., within a predeterminedgeographic proximity). As a result, the end user does not have to gothrough tedious manual operations in order to reach out someone who isnearby and familiar with the content in question or someone who he orshe can talk to immediately concerning the content at the point in time.

According to one embodiment, when a user accesses content presented by acontent server (e.g., Web server such as a Yahoo® or Google® Web server,also referred to as a content presentation server), the content servermay communicate with a live content (also referred to as live sponsoredcontent) server (e.g., Ad network) to request a list of live content(e.g., live connect Ads) that is associated with the information orcontent currently accessed by the user (e.g., search term, keyword, orsearch result). In response, the live content server identifies, forexample, from its content database, a list of live content associatedwith the information the user is currently interested in (e.g., searchinformation, user information). For each of the live content, the livecontent server communicates with a live connect server to determinewhether there is another user or at least one specialist (also referredto as subject matter expert or SME, support agent or simply agent)currently available, who is familiar with the subject matter in questionand who can communicate with the user at the point in time. For each ofthe inquired live content, the live connect server identifies zero ormore specialists that are currently available, for example, based on thegeographic locations, presence information, and status of thespecialists, which may be stored and periodically updated in a user orspecialist database associated with the live connect server.

The live connect server returns information indicating which of the livecontent that has at least one live support person or agent (e.g.,specialist) available. In one embodiment, the live connect serverreturns identifying information of the live support persons that areassociated with the live content being inquired (e.g., live Ads). Foreach of the associated support persons, for example, prior to presentingthe live content, the live connect server further determines whether therespective support agent is currently available, and if the supportagent is currently available, the respective geographic location (e.g.,longitude and latitude data) with respect to the geographic location ofthe visitor. For each of the live content that has at least one supportagent available, according to one embodiment, the live content may bepresented to the user by the live content server and/or the contentpresentation server. In addition, each live content may be presentedwith a live connect button or control to enable the user to contactanother user that is associated with the live content. In oneembodiment, an available specialist may also be someone located within apredetermined geographic proximity with respect to a geographic locationassociated with the visitor. For example, an available agent can contactthe visitor discussing the live content in real time or within a veryshort period of time, and potentially go to and arrive at a premises orproperty (e.g., house or building) of the visitor within a reasonableperiod of time, for example, to provide services related to the livecontent, which may also be desired or expected by the visitor.

Alternatively, according to another embodiment, each live content may bepresented with identifying information of one or more support agents orspecialists who can communicate with the visitor immediately or within ashort period of time for discussing the corresponding live content. Inone embodiment, the identifying information includes a name and/or apicture of the specialist and a geographical location of the specialistwith respect to the user. One or more of the available specialists arepresented to the user with a live connect button or control. Thedisplayed live content may also indicate that the user can contact aspecialist or agent associated with the live content in real time andguaranteed to reach a live person within a short period of time. Theuser can activate or click a live connect button or control to contactthe corresponding specialist at the point in time, for example, based onthe geographic location of the specialist or based on reputation of thecompany the specialist is associated with. If particular live contentdoes not have at least one specialist that is currently available, thatparticular live content may not be presented to the user or the contentis presented as static content without indicating that the user cancontact an agent in real time. This ensures availability of bothparties—the user who would initiate a connection and the specialist whomust be available to accept/respond to communication—and is dependentupon the specific configuration or rules of the content server.Alternatively, that live content may be presented as regular staticcontent, for example, without presenting the live connect button orcontrol, when there is no specialist currently available. In such asituation if subsequently there is a specialist who becomes available,the live connect button or control is then presented to the user, againdependent upon the specific implementation or configuration of thecontent presentation server and/or content distribution server.

When the visitor activates or clicks on a live connect button of aparticular live content, a connection request is transmitted to the liveconnect server. The request may include contact identifying informationof the visitor (e.g., name, address, phone number, email, etc.) andother user information (e.g., search information, activities performedby the visitor, and/or a geographic location of the visitor). Inresponse, the live connect server routes the visitor's information to aspecialist who is associated with the live content and is alsoavailable. In one embodiment, a specialist may be selected, for example,based on its availability status and/or its geographic location, by thelive connect server when the live content server requests foravailability information. As a result, the identifying information ofthe selected specialist may have been embedded as part of executablecode associated with the live connect button. Thus, when the visitoractivates the live connect button, the underlying code is executed and adata message is transmitted to the live connect server, which in turnroutes the information to the selected specialist. That is, a specialisthas to be selected before the live content is displayed. That matters intwo ways: (1) in order to display a map of specialists the specific andunique geographic information for each specialist must be ascertained;(2) chat or call information must be determined and embedded in part ofthe live content code. In this situation, the live connect server canautomatically routes the request to the selected specialist without userintervention. The selected specialist can then respond to the connectionrequest at the point in time. Alternatively, according to anotherembodiment, the visitor can initiate a contact request by activating thelive connect button, as a general live connect button to connect withthe live content owner, to communicate with a dispatcher or managerassociated with that particular live content, which in turn selects androutes the contact request to a specialist who is available. In thissituation, a dedicated person, such as an administrator, a manager, or adispatch person has to be available to receive the request and determineto which of the available specialists the request should be routed. If aspecialist becomes unavailable or is unwilling to accept the request,the request may be rerouted to the dedicated person, such as adispatcher, manager, or a dedicated overflow specialist.

FIG. 1 is a block diagram illustrating a network system providing liveconnect services according to one embodiment of the invention. Referringto FIG. 1, system 100 includes, but is not limited to, one or moreclient devices 109, one or more service provider devices 113, livecontent servers 101 and content/data servers 105 communicatively coupledeach other over network 107. Client devices 109 and/or service providedevices 113 may be any type of data processing devices such as a server,a personal computer (e.g., desktops, laptops, and tablets), a “thin”client, a personal digital assistant (PDA), a Web enabled appliance, agaming device, a media player, or a mobile device (e.g., Smartphone),etc. Content/data servers 105 may include web servers, applicationservers, content servers or other servers providing remote services(e.g. Web search, cloud storages, gaming, social networking etc.) forusers of client device 109. Network 107 may be any type of networks suchas a local area network (LAN), a wide area network (WAN) such as theInternet/intranet, cellular networks, secured/open networks,wired/wireless networks or a combination thereof.

In one embodiment, live content server 101, as a content distributionserver, provides live content services, such as, for example, Adservices, for content presentation servers 105 to leverage Adopportunities via content or services offered to client devices 109.When content server 105 presents content to users, in addition topresenting regular static content (e.g., search result), content server105 communicates with live content server 101 to inquire any livecontent of a specific type (e.g., content related to those the users arecurrently interested in). Live content server 101 in turn identifies alist of live content, which may be configured previously forparticipating in particular live content distribution (e.g., Adcampaign). For each of the identified live content, live content server101 (e.g., Ad server) communicates with live connect server 103 todetermine one or more specialists that have been registered with liveconnect server 103 and are currently available to contact the users whomay be interested in the live content. In response, live connect server103 identifies zero or more of the specialists that are available andtheir respective geographic locations. The information of the availablespecialists is then transmitted back to live content server 101 and thelive content having at least one available specialist may then bepresented to the users. The users can then access the live content andcontact with the available specialists for further discussion about thelive content Ad.

According to one embodiment, in the field of advertising, the livecontent may represent Ads from which a visitor can contact a specialistassociated with the Ad. Live content server 101 may represent Adinfrastructure, Ad networks, Ad servers, and/or Ad exchanges for servingadvertisements via content servers 105 to client devices 109. Liveconnect server 103 may offer live connect Ads via Ad services 101 toallow a user of client device 109 to communicate in real time (e.g.live) with a specialist of an advertiser of the live connect Ads. Liveconnect server 103 may include a live connect system to interface withlive content server 101 and availability system to select/facilitateavailable specialists for establishing live communications, for example,between client devices 109 and service provider devices 113, to renderan advertised or requested service to the user of devices 109 by aspecialist using service provider devices 113.

The live content can be a variety of information, such as, for example,Ads sponsored by various Ad providers. The real-time live connect Adservice can provide a solution that allows a visitor (or a user) toaccess a live specialist (e.g. nearby a live person) via a communicationlink established from an advertisement presentation (e.g. live content)via a desktop device, a mobile device, a phone device or other devices.For example, a visitor may be presented with an Ad via a search on thenetwork (e.g., Internet) from their desktop or mobile browser, for aspecific support or service need. An Ad integrated into a real-timeconnected Ad service can be presented to the visitor. From interactionswith the Ad presentation, the visitor can be connected with an availablelive support or service person to provide services. Live connect Adservices may be applicable for different kinds of services in varioustypes of businesses.

In one embodiment, existing Ad services may be augmented with the livesupport and service capability when integrated with real-time liveconnect Ad service. A visitor can select a live connect Ad (or real-timelive connect Ad) to automatically connect with a live person or servicein real time without a need to make additional contact request. Aregistered specialist can be connected to the visitor when the Ad isselected (e.g. clicked) within a short time period (e.g. 5 or lessminutes or other applicable specified time period) or a scheduled timeperiod without requiring the visitor to wait for later and/orunspecified date/time by way of filling out a form or sending an emailto the business advertising services. Live connect Ad service canperform analytics on data received from existing Ad services (e.g.originated from a client device used by a user or a visitor) to provideintelligent routing between the visitor and a highly skilled specialist.For example, the data may include presence and geo-location informationto allow the live connect Ad service to present those specialists whocan meet up with the visitor for specific services.

Live connect Ad solution (service) can make intelligent decisions toserve live connect Ads with a multitude of situational and presencebased capabilities. For example, a live connect Ad of a company (or aservice provider, a specialist) may be presented to a visitor at aspecific day and time based on whether a live person of the company isavailable. A live connect Ad for a specialist may be presented (orserved) when this specialist is available to talk real-time once the Adis clicked through via the visitor (or user).

In one embodiment, the availability of a specialist for presenting alive connect Ad to a visitor may be determined based on (but not limitedto) presence of the specialist, location of the specialist, geographicproximity between the visitor and the specialist, expertise of thespecialist, and/or other applicable information made available. Presenceof a specialist may be based on a presence indicator managed (orupdated) by the specialist (e.g. when logging into a management systemfor the live connect Ad service management system). Location of aspecialist may be based on the current geo-location of the specialistcollected from an associated mobile device. Proximity between a visitorand a specialist may be determined based on geo-locations detected orcollected from separate devices used by the visitor and the specialist.

In one embodiment, if the specialist and the visitor are in differentgeographic locations (e.g., different states) yet the specialist ispresent and available and can service the visitor (virtually) withoutmeeting face to face, then a live connect Ad can be offered or served tothe visitor to establish a communication link in real time between thespecialist and the visitor on the visitor's request. However, if a faceto face meeting is required for a service provided by the specialist, nolive connect Ad of this remote specialist (with respect to the visitor)would be offered to the visitor. The live connect Ad system may includeconfigurations or settings including business rules or knowledge, forexample, specifying which specialists (or companies) can serve visitorsremotely or face to face (i.e. locally) according to requirements of theservices provided.

Service campaigns (or advertisements) for a specialist or a company maybe configured with proximity settings, for example, to only allow faceto face meet up with a visitor, only allow virtual meet up (e.g. onlineconnections) with a visitor, allow a mix of face to face and virtual metup with a visitor, or apply other applicable constraints orrequirements. If a face to face meet up is required, as an example, alive connect Ad for a specialist can be served to a visitor if thespecialist and visitor are in the same state (within a specifieddistance from the visitor) and the specialist is present and available.

In some embodiments, availability of a specialist (or company) maydepend on time (or schedule) required or indicated by a visitor to meetface to face with the specialist. The live connect Ad service canidentify multiple factors, such as travel time, type of urgencies, etc.to determine whether a certain specialist can be available for thevisitor. The live connect Ad service can extract a schedule request froma visitor (e.g. based on search terms) to select which specialists (e.g.via Ad campaign settings) are available for the requested schedule (e.g.day/time) to provide possible services to the visitor (e.g. face to faceor online).

FIG. 2 is a block diagram illustrating a networked system for providinglive content according to one embodiment of the invention. System 150may be implemented as part of system 100 of FIG. 1. Referring to FIG. 2,system 150 includes, but is not limited to, content server 151 (e.g.,content presentation server) to present content to end users or visitorswho access the content from client devices 154. Content server 151 iscommunicatively coupled to a live content server 152, which is coupledto live connect server 153. Content server 151 may be a Web server thatpresents content to the client devices 154, such as, for example,Yahoo®, Google®, or social networking Web servers. The content presentedby content server 151 may include regular static content 161 and liveconnect content 162.

According to one embodiment, when a visitor associated with clientdevice 154 accesses, via its corresponding client application 181,content presented by content server 151, based on the user interactionwith the content server 151, for example, interaction with staticcontent 161, content server 151 communicates with live content server152 to request live content, such as live content 162 to be presented tothe visitor. In response to the request, live content server 152identifies one or more live content that are eligible or related to therequest. For each of the identified live content, live content server152 communicates with live connect server 153 to determine whether thereis at least one specialist or user that is currently available to have alive communication with the visitor.

Live content server 152 may maintain a content database that stores allthe live content that have been registered and configured by differentlive content owners or administrators, in this example, represented byclient device 156. In one embodiment, for each of the live content thatis identified based on the request, live content server 152 transmits arequest to live connect server 153, including a live content itemidentifier (ID). Based on the content ID, availability module 171 (alsoreferred to as availability unit or logic) of live connect server 153identifies a list of specialists or support agents who have beenpreviously configured for providing live support to that particularcontent. For each of the specialists, availability module 171 determineswhether that specialist is currently available to have a livecommunication session with the visitor at the moment and the geographiclocation of the specialist. The availability module 171 determines theavailability of the specialists using presence services provided by apresence engine, which may be implemented locally or remotely via athird party vendor, status or state of the specialists, and/orgeographic locations of the specialists.

In one embodiment, information indicating whether a particular livecontent has at least one available specialist is transmitted from liveconnect server 153 to live content server 152. Alternatively, a list ofzero or more specialists that are currently available is transmittedfrom live connect server 153 to live content server 152, including thegeographic locations of the specialists (also referred to as a subjectmatter experts or SMEs). In response to the list of zero or morespecialists, live content server 152 selects an appropriate subset ofthe eligible live content and transmits the selected live content tocontent server 151 to be presented as part of live content 162 tovisitors. Alternatively, the selected live content may be directlytransmitted to client device 154, which may be integrated with thecontent delivered by content server 151 by client application 181. Inaddition, according to one embodiment, the list of one or more availablespecialists or support agents that are associated with the presentedlive content may also be presented, including their respectivegeographic locations. The geographic locations of the specialists may bepresented in a map with respect to a geographic location of the visitor(optionally with a geo fence or predetermined geographic proximity).According to one embodiment, a live content owner may specify orconfigure a set of rules (not shown) under which the corresponding livecontent may or may not be presented. For example, if there is nospecialist currently available, the content owner may decide not topresent the live content or alternatively, the content owner may specifyin the rules to allow the live content to be presented as static content(e.g., static content without presenting the live connect button orcontrol) if no specialist is available.

According to one embodiment, for each of the live content 162 presentedby content server 151, there is a corresponding live connect button orcontrol to allow the visitor to contact the corresponding specialist fora live communication session discussing the subject matter of the livecontent 162. The live communication session can be established using avariety of communications methods or channels, such as, for example,voice, chat, text, Web conferencing, or social media, etc. The visitorof client device 154 may select and contact one of the presentedspecialists by activating or clicking the corresponding live connectbutton or control. In response to the activation or click of the liveconnect button, live connect module 172 (also referred to as liveconnect unit or logic) of live connect server 153 obtains userinformation associated with the visitor and routes the information ofthe visitor to a specialist currently available, in this example,represented by client application 182 of client device 155. The userinformation of the visitor may be collected from the visitor directly,for example, using an interview or dialog engine to prompt the visitorfor contact information of the visitor. In response, the specialist canestablish a live communication session with the visitor for discussingthe live content in question. This is done by the SME clicking a buttonto accept the request and call (or message) the visitor. Alternatively,when the visitor clicks the live connect button, a call is directly madebetween client device 154 of the visitor and a dedicated personassociated with the Ad (e.g., administrator or job dispatcher). Thededicated person can then select one of the available SMEs. If theselected SME accepts the assigned job, the user information is routed tothe selected SME and a live communication session is established.

Since live content is presented dependent upon the availability of theassociated specialists and the available specialists may becomeunavailable from time to time, the presented live content may becomeexpired after a predetermined period of time if the visitor does notinitiate a live contact by clicking the corresponding live connectbutton. The rationale behind it is that a specialist may supportmultiple live Ad campaigns or a single Ad campaign but presented atmultiple content presentation servers and/or multiple live contentservers. A specialist may accept a live communication request at anymoment of any of the live content, which causes the specialist becomingunavailable. As a result, when a visitor clicks a live connect button,if the corresponding live content has expired, the live content may berefreshed by the content presentation server and/or live content server,in which the live connect server is invoked to determine theavailability of the specialists for the same live Ads again.

According to one embodiment, system 150 may be utilized to provide liveadvertising from various advertisement providers. For example, livecontent server 152 may represent an Ad server and/or Ad network in whichan advertisement owner can set up and configure an advertisement to bedistributed by Ad server 152. The advertisement owner can also configurea set of one or more specialists in live connect server 153 that areassociated with the advertisement presented by Ad server 152. Contentserver 151 may be a Web server that provides information accessed to avisitor represented by client device 154.

For example, content server 151 may be a Web server with a search engine(e.g., Yahoo or Google search Web site). As an Ad owner, a plumbingcompany may set up an Ad account in Ad server 152 having a plumberrelated advertisement. In addition, the Ad owner may further set up oneor more plumbers as specialists or agents for the plumber advertisementin live connect server 153, including registering their client devices155 and communication methods to contact them. When visitor 154 performsa search of a keyword, such as, “I need a plumber,” via a search engine,the Ad server 152 will identify the Ad setup for “plumbing,” and collectspecialist availability from live connect server 153, pass informationto content server 151 which would transmit information representing whatthe visitor is currently interested in, in this example, plumber, tolive content server 152 for inquiring any advertisements related toplumber. Based on the request, live content server 152 searches in alive content database (which is stored in a persistent storage such as ahard drive of a data processing system) to identify a list ofadvertisements that have been previously registered and associated withthe keyword in this example. For each of the identified advertisements,live content server 152, as an Ad network, communicates with liveconnect server to determine a list of specialists that are associatedwith the Ad in question. For example, server 152 may send an Ad ID toserver 153 to request a list of specialists currently available for thatparticular Ad identified by the Ad ID. Sever 152 may further send userinformation of the visitor to live connect server 153, such as, forexample, name, address, and/or geographic location of the visitor.

Availability module 171 of live connect server 153 determines zero ormore specialists that are currently available based on their respectivegeographic locations. The list of available specialists and theirgeographic locations are sent back to live content server 152. Livecontent server 152 then transmits the live connect advertisement toclient device 154 via content server 151 or directly to client device154 to be integrated by client application 181 therein. A live connectAd may be presented with a corresponding live connect button or controlto allow the visitor to contact an available specialists. In oneembodiment, only the advertisements that have at least one specialistavailable are presented to the visitor 154; otherwise, the advertisementmay be presented as static advertisement, for example, without liveconnect buttons or suppressed all together based on the Adconfiguration.

According to another embodiment, content server 151 may be socialnetworking server (e.g., Facebook®, Twitter®) in which Ads are displayedto their users. Users may interact with the social networking server andbased on the user interaction with the social network, server 151 maycommunicate with live content server 152 to obtain a list of liveconnect advertisements associated with available specialists. The userscan contact the available specialists from the advertisements at thepoint in time. For example, when a visitor interacts with a social Website, for example, by typing “need a plumber, can someone help?” theuser interactions are monitored by the social Web site. In response, thesocial Web site creates a search package with one or more search terms,and pushes the search package back to a client device of the visitorprompting the visitor to click a search link presented by the searchpackage. When the visitor clicks on the link, it causes browser to bedisplayed and a search is performed according to the search package. Thesearch request is received by a predetermined search engine and theabove processes are then performed amongst the search engine, the livecontent server, and the live connect server, as described above.

Note that the system configuration as shown in FIG. 2 is described forillustration purpose only. Other configurations may exist. For example,content server 151 and live content server 152 may be implemented as asingle server or a cluster of associated servers (e.g., within the samedomain). Live connect server 153 may be integrated with a server or acluster of servers representing a support center. A multi-channelcommunication system associated with a support center can be utilized toestablish a communication session between a visitor and a specialist.Similarly, an Ad owner can utilize other resources of the supportcenter, such as, the infrastructure of the support service system (e.g.,multi-channel communication system, support agent management androuting, data analytics capability, presence service, etc.), to providesupport services to the advertisements.

FIG. 3A is a block diagram illustrating a networked system for providinglive content according to another embodiment of the invention. Thesystem as shown in FIG. 3A may be implemented as part of system 100 ofFIG. 1 or system 150 of FIG. 2. Referring to FIG. 3A, in thisembodiment, content server 151 represents a Web server having searchinginterface 175 and an associated search engine (not shown). For example,content server 151 may be a Yahoo®, Google®, or Microsoft Bing™ server.In this example, assuming a visitor visits a search Web page presentedby search interface 175 of Web server 151 and submit a search query viatransaction (1). Based on the search query, the search engine associatedwith Web server 151 performs a search to generate a search result. Inaddition, according to one embodiment, Web server 151 sends a request,via transaction (2), to live content server 152 for any live contentthat is associated with the search query (e.g., search term and otherterms having the same or similar meaning).

In response to the request for live content, live content server 152searches a live content database maintained therein (not shown) toidentify a list of live content that is associated with the searchinformation provided by content server 151. The live content has beenpreviously configured or registered by the corresponding live contentowners or administrators. For each of the identified live content, livecontent server 152 transmits a request to live connect server 153, viatransaction (3), for availability information of SMEs associated withthe specific live content. The request may include a content IDidentifying the live content and optional some visitor information(e.g., geographic location of the visitor). In response, live connectserver 153 identifies a list of zero or more of SMEs that are availableat the point in time. Live connect server 153 may search in an SME oragent database (not shown) based on SME information, such as, forexample, SMEs' status (e.g., SMEs with status of “available”),geographic location of the SMEs, and skill set (e.g., Ad campaignconfiguration), etc. Live connect server 153 returns the list of zero ormore available SMEs back to live content server 152 via transaction (4).

Based on the available SMEs provided by live connect server 153, livecontent server 152 determines a list of one or more live content to bepresented to the visitor. In one embodiment, only the live content thathas at least one SME available will be represented to the visitor.Alternatively, if multiple live content having available SMEs areassociated with the search information, live content server 152 mayselect a subset that are most appropriate under the circumstances. Forexample, if a search result page provided by content server 151 only hasenough space for two Ads, live content sever 152 may select two of themultiple live content that have SMEs whose geographic locations closestto the geographic location of the visitor. The selection of the livecontent may also be upon other data or rules (e.g., privilege ormembership level of the live content owners).

The search result, as well as the live content, is then delivered toclient device 154 and presented to the visitor by client application181. In one embodiment, the live content may be transmitted by livecontent server 152 to client device 154 directly via transaction (5),while the search result is delivered to client device 154 by contentserver 151 via transaction (6b). The live content is then rendered andincorporated with the search result by client application 181. In thisembodiment, content server 151 may instruct client application 181and/or live content server 152 by indicating in the search result thelocation and size of space for presenting the live content. In return,live content server 152 transmits executable code (e.g., HTML, XML,JavaScript, etc.) to client application 181 to allow client application181 to render the live content and incorporate the live content with thesearch result. Alternatively, according to an alternative embodiment,live content server 152 sends information representing the live contentto content server 151 via transaction (6a). Content server 151integrates the live content with the search result and sends the searchresult with the live content integrated therein to client device 154 viatransaction (6b).Furthermore, when content server 151 sends the requestfor live content via transaction (2), it may also send the search resultpage to live content server 152. The live content server 152 isresponsible to render the live content with the search result and sendsthe integrated search result to client device 154 via transaction (5).Other configurations may exist.

According to one embodiment, when the visitor activates the live connectbutton presented as part of the live content, a live connect request istransmitted to live connect server 153 via transaction (7). That is,when the visitor clicks the live connect button, the underlyingexecutable code is executed and as a result, the request is sent to apredetermined destination address, i.e., live connect server 153 or aspecific SME (e.g., SME or agent device 155). The live connect requestmay request for a text, voice, chat communications session. If the liveconnect button has been configured as a voice connection, when thevisitor clicks the live connect button, a data message is transmitted tolive connect server 153 and routed to a predetermined SME, in thisexample, SME device 155 via transaction (8). The data message mayinclude a phone number of the visitor. When client application 182 ofSME device 155 receives the message, the SME can simply click the phonenumber to initiate a voice call with the visitor. For text or chatcommunications method, the SME can invoke the corresponding text/chatapplication to establish a text/chat communications session with thevisitor, in this example, client device 154 via transaction (9).Alternatively, the live communications session may be established by amulti-channel communications system, for example, as part of a supportcenter associated with live connect server 153.

According to one embodiment, if the SME becomes unavailable or isunwilling to accept the request, the request is routed to apreconfigured dedicated person, which may be an overflow SME, anadministrator, or a dispatch person. If the request is routed to adispatcher, the dispatcher can select another SME from a dispatch or SMEmanagement interface and causes the request to be routed to thealternative SME. The dispatcher can also accept the request andcommunicate with the visitor. When the SME accepts the request throughclient application 182, the client 182 may automatically communicatewith live connect server 153 to change its status, for example, from“available” to “unavailable.” By changing the status from “available” to“unavailable,” a subsequent request will not be routed to the same SME.This may also change the availability of the associated live content tobe presented to another visitor. The status and states of the SMEs aremaintained by live connect server 153 in an SME or agent database (notshown).

In one embodiment, live connect server 153 further includes an SMEmanagement module or manager that is responsible for registering SMEsand tracking the status and states of the SMEs. A client application ofan SME device (e.g., client application 182 of SME device 155) mayperiodically communicate with the SME management module to update thestatus and states of the SME, which will be stored in an SME database.The SME manager can access the information stored in the SME databaseand perform certain management actions, such as taskforce management byallocating different SMEs to different jobs or Ad campaigns for workloadbalance purposes.

The SME manager may further communicate with the customer in view of thestatus or states of the SMEs. For example, when an SME goes tocustomer's premises for performing a job that has been negotiatedbetween the SME and the customer, the SME may set its state via itsclient application of the SME device to “on-the-way-job-site” state inthe SME database. In response, the SME manager or some other componentsmay dynamically set up a geo-fence (e.g., a geographic proximity withcertain size) and tracking the physical movement of the SME. Forexample, the SME management system may periodically receive locationinformation from the application running within SME device (e.g., clientapplication 182 of SME device 155). The location information may beobtained by the client application from an operating system of the SMEdevice. In one embodiment, when the SME enters the geo-fence, the SMEmanagement module sends or pushes SME information to customer's clientdevice (e.g., visitor device 154). The SME information may include apicture of the SME and other identifying information of the SME and thejob to be performed. As a result, the customer can positively know whohe or she is dealing with for security reason. By monitoring the statusand states of SMEs, the SME manager can proactively manage theavailability of the SMEs and proactively engage with the customers tofurther improve customer's satisfaction.

FIG. 3B is a block diagram illustrating a networked system for providinglive content according to another embodiment of the invention. Thesystem as shown in FIG. 3A may be implemented as part of system 100 ofFIG. 1 or system 150 of FIG. 2. Referring to FIG. 3B, in thisembodiment, content server 151 represents a social networking server(e.g., Facebook®, Twitter®) in which a user or visitor can post orreceive a social post message, such as social posts 176. In oneembodiment, social networking server 151 includes social post monitor177 to monitor and analyze social posts 176. In one embodiment, when avisitor posts a social post via transaction (1), social post monitor 177detects and analyzes the post and may determine that the visitor islooking for certain service such as plumbing services. For example, thevisitor of client device 154 may chat with a friend concerning aplumbing problem at his or her house. Social post monitor 177 monitors,detects, and analyzes the chat information, and determines that thevisitor may need a plumber coming to his or her house to fix theplumbing problem.

In response, social post monitor 177 sends a message with a link toclient application 181 of client device 154 via transaction (2). Themessage may include a button, link, or control to prompt the visitorthat the visitor can find a plumbing specialist who is currentlyavailable and possibly nearby. The visitor can activate the link orcontrol, which in turn sends a message to live content server 152 viatransaction (3). The link or control may be generated by social monitor177 including underlying executable code, which when executed (e.g., byactivating the link or control), sends a message to a predetermineddestination, in this example, live content server 152). The message mayinclude information describing the requested content information (e.g.,plumbing and/or related services), as well as certain informationconcerning the visitor (e.g., geographic location of the visitor). Thevisitor information may also be obtained via information from thevisitor's social networking account provided by social networking server151. In response to the message received from client device 154, livecontent server 152 identifies a list of live content that have beenregistered with the live content server 152, and the rest of operationsinvolved in transaction (4) to transaction (9) are performed similar tothose involved in transaction (3) to transaction (9) of FIG. 3A. Notethat an Ad is utilized as an example of a live content throughout thisapplication. However, the techniques described throughout can also beapplied to other types of content, such as, for example, media content,documents, presentations, etc.

FIG. 4 is a block diagram illustrating a live connect system forproviding live connect services according to one embodiment of theinvention. For example, the system as shown may be hosted in anoperating environment or an operating system running in one or moreserver devices (or machines). For the purpose of illustration, live Adservices are utilized as examples of live connect services. In oneembodiment, live connect server 153 may include live content interfacemodule or logic 203 providing generic interface support to external Adnetworks (or servers, infrastructures). For example, transactions ordata/message exchanges between live content interface module 203 andexternal Ad servers may be based on live connect service API(application programming interfaces) 235. Visitor related data (e.g. IPaddress or other data extracted from client browsing activities) may bepassed to system 153 via live connect service API 235.

Interface module 203 may include live connect live content managementmodule 205 to manage content/data included in live connect Ads based on,for example, Ads templates stored in a database or storage device. Liveconnect management module 205 can filter a list of requests (e.g. eachrequest associated with a business) for live connect advertisingreceived from an external Ads network according to whether associatedspecialists are available (e.g. via availability module or logic 211)and/or other configured selection criteria (e.g. via live connect moduleor logic 207). No live connect Ads will be provided for these requestsif no specialists are available at the time these requests are received.Note that live connect interface module 203 may also be implementedwithin an Ad server such as server 152 of FIG. 2.

In one embodiment, executable code (e.g. script or other applicableinstructions executable in a client device) may be embedded in a userinterface element (e.g. a button, link, or control) generated via liveconnect management module or logic 205 to allow establishment of livecommunications. The code may include timer mechanism that willautomatically expire if the user interface element is presented to aclient device for a specified period of time without receiving userinputs (e.g. clicking on a live connect button). When expired, the userinterface element may be automatically updated, for example, to ask auser (e.g. a visitor) of the client device to cause a refresh of theuser interface element (e.g. sending another request directly to system201 or a web server coupled with system 201, etc.).

Availability module 211 can determine whether there is a match, no matchor degrees of match between a specialist and a visitor. For example,presence engine presence determination logic 215 can determine whether aspecialist (or a group of specialists) is currently registered forproviding services via live communications and the current state of thespecialist. A specialist may be available if this specialist isregistered and also in an “available” state (which can change in realtime). Geo location engine or location determination logic 217 canidentify or track current locations of the visitor(s) and thespecialists. In some embodiments, geo location engine 217 can providerouting guidance and/or dynamic vicinity area, such as geo fence of thevisitor, to facilitate face to face meeting between a visitor and aspecialist.

The geo location engine 217 may perform operations to capture, extractand or identify location and tracking information for both a visitor aswell as specialists of the support or service. For example, geo locationengine 217 can obtain geo location information of the specialists andvisitors via external location service providers, through an interviewwith the visitors and/or specialists, and/or other user actions.Alternatively, geo location engine 217 may communicate with a clientapplication running with a client device of the specialists and/orvisitors to obtain geo location information and determine the geographiclocation in real time. The presence engine 215 may determineavailability of a specialist or a group of specialists to support orservice a visitor at the time a request is made, for example, via thevisitor's clicking through on a custom ad (e.g. a live connect ad). Oncea specialist is identified and selected, the live connect Ad system canroute the visitor to the specialist to establish a communication link.The geo location engine 217 may perform operations to support Ad basedlive interactions by collecting location information for both thevisitor and the specialist. For example, current locations of thevisitor and specialists may be identified and/or updated (e.g. tracked,monitored) via the geo location module. A specialist that is locatedwithin a local vicinity of the visitor may be recommended based on ananalysis (e.g. via DAE module) on the identified location information.

In one embodiment, the identified (e.g. real time monitored) geolocation information of both the visitor and the specialist may beleveraged to provide navigational guidance for the specialist to travelto the visitor's location for face to face meetings, work to beperformed, etc. A geo-fence may be created (e.g. dynamically via thelive connect ad service) around the visitor's location to allow sendingtimely notifications to the visitor of the specialist's arrival at themeeting or work place. A specialist's information and photo may be sentto the visitor for verification and security purposes.

The presence engine 215 may identify whether a specialist is currentlyregistered on the support center system for the live connect ad serviceand in which state (e.g. indicating availability) the specialist iscurrently. The live connect ad service may automatically include orexclude the specialist for establishing a communication link with avisitor based on the state of the specialist. For example, if thespecialist is in a state (or status) other than “available”, the visitorwill not be informed of this specialist for further their interactions.States other than “available” or non-available states for the specialistmay include, for example, not-available, on a call, in meeting, on job,off-site, in training, or other applicable states. The specialist may beassociated with one single state at a time. A visitor may not beroutable to a specialist currently in an unavailable state.

The state or status settings (e.g., terms for states and/or status) maybe customized to the specific needs of an owner of specific live content(e.g., specific Ad campaign). Each company of the live content may havedifferent state and/or status definitions and rules associated with thestates and status. Each live content of the same company (e.g., Adcampaign) may have different states and status settings. The customizedstates and status may be presented and set via the client application ofan SME who has been associated with or assigned to a specific livecontent. As described above, an SME may be associated with multiple Adcampaigns, dependent upon which of the associated Ad campaigns the SMEcurrently logs into, the terms, definitions, and/or rules of the statesand status may be the same or different. An administrator or owner ofthe live content can configure such terms, definitions, and rules via amanagement or administration interface or portal (not shown) of liveconnect server 153, and the terms, definitions, and rules of the statesand status can be stored as part of a client account of client database234 maintained by live connect server 153.

Data analytics engine (DAE) or data analyzer 213 can perform analysisoperations on data collected for a visitor from various sources, such asvisitor data passed via interface module 203 and/or visitor dataidentified via live connect management module 207. Data analytics engine213 may include customized algorithms or rules selectively applied forthe analysis operations as instructed. In one embodiment, SME selectionmodule or logic 219 can determine which specialist(s) best match avisitor based on analysis results of data analytics engine 213. Forexample, SME selection module 219 can select a specialist from multiplespecialists available for an onsite service requested by a visitor (e.g.via a live connect Ad) ranked by data analytics engine 213 based oncloseness or accessibility of geo locations related to the visitor andthe specialists.

DAE 213 can analyze available data to determine or select applicablelive connect ads for a visitor. Data utilized by DAE may include datacollected from a client device (e.g. used by the visitor) based onclient actions (e.g. search actions or user behavior) via a clientapplication (e.g. a browser), geo-locations of the client device,geo-locations of the specialist (e.g. via an associated mobile device),and/or other pertinent data. DAE module may be configured with differentanalysis algorithms for different live content to perform customizeddata analysis created for the corresponding businesses.

For example, DAE 213 can analyze Ads related data passed to the liveconnect Ad service (e.g. a support center) to determine a best routebetween a visitor and a specialist (e.g. to meet up with the visitor orestablish a communication link with the visitor). Optionally oralternatively, DAE can analyze, in real time, data collected viainterview engine 237, or interview data, geo information and/or presenceinformation to identify the best route via custom models based on thedetails and/or output events interpreted by the system as navigationand/or routing instructions for the best skilled specialist matching thevisitor's requirements. DAE may analyze combined Ads related data andinterview data for the best route.

In one embodiment, live connect routing module or logic 227 may exchangemessages with a client device, e.g. based on embedded code in a liveconnect button, used by a visitor to establish a real time livecommunication between the visitor and a specialist. For example, liveconnect routing module 227 may receive a message from the client devicevia the embedded code for presenting a live connect button of a liveconnect Ad to the visitor. Live connect routing module 227 may determinewhether any specialist associated with the live connect Ad is currentlyavailable via availability module 211. Depending on whether there arelive specialists available (e.g. available and local to the visitor),the live connect button may be presented differently. For example, thelive connect button may not be presented if there is no specialistcurrently available. If there are specialists available, live connectrouting module 227 may exchange messages with the client device toestablish a live communication link between the client device and adevice used by a specialist selected via, for example, availabilityhandler module 211.

System 153 may include live connect module 207 to maintain/manage datarelated to visitors and specialists. For example, content (e.g.,advertiser) management module or logic 209 can provide administrativeinterfaces for businesses or specialists registered for live connect Adservice. Content management module 209 may include or couple with ademand-side platform or DSP to interface with multiple external content(e.g., Ad) exchanges or infrastructures. Visitor data management moduleor logic 221 can extract visitor related data from requests receivedfrom the live content server, such as for example, Ad servers (e.g. liveconnect Ad requests) or visitor client devices (e.g. button clicks). Insome embodiments, visitor data management module 221 may include orcouple with a data marketing platform or DMP to identify visitor datafrom multiple sources, for example, applicable for availability decisionand/or specialist selection in availability module 221. Interview engineor logic 237 may be activated to solicit (e.g. via user interfacespresented in a browser application of a client device used by a visitor)additional visitor information in real-time.

In one embodiment, rule engine 225 may include custom configurations orsettings which can be leveraged or referenced for customizable dataanalysis and/or visitor routing to a specialist (e.g. matching thespecialist with the visitor). Optionally, interview engine 237 mayenforce custom interviews to be required of visitors to collectadditional information that can be utilized for routing to a specialistor for information the specialist can leverage within the interactionwith the visitor. Feedback engine 229 can facilitate social postingsfrom a visitor. For example, comments, experience or a few words abouttheir experience from a visitor upon completion of an interaction with aspecialist (via a company's Ad) can be posted to a variety of socialsystems such as Facebook™, Twitter™, Instagram™, Linked In™, etc., viathe social feedback engine.

According to one embodiment, live connect module or logic 207 mayinclude SME management module or logic 223 for registering and trackingspecialists providing services advertised over live connect Ad services.For example, SME management module 223 can provision a specialist forparticipating in live connect Ad service. SME management module 223 maytrack job status and/or current states of specialists via mobileapplications running in client devices used by specialists. SME DB 223may store registration information of specialists/businesses and/orcurrent states or related information tracked real-time for thespecialists. Business rule engine 225 may include configurablesettings/rules to control operations performed in live connect Adservices.

For example, the business rules may be applied to determine (orenable/disable) visibility of the live connect button when no agents (orspecialists) are present, visibility of the live connect button when noagents are available even though they are present, whether to enable ordisable button image change based on specific prequalification states orvalues associated with the visitor (e.g. the user presented with thelive connect advertisement). Different button image may be displayedbased on analysis data via DAE and/or a visitor's prequalification.

Business rules may include setups or settings in the live connect Adsystem to allow or restrict a specific capability or feature related toentities such as a visitor and/or a specialist. Exemplary setups mayinclude enabling/disabling capabilities related to:

Geo-location of visitor and/or specialist:

-   -   Using visitor location information    -   Using visitor address on file in place of geo data    -   Matching a visitor to a local specialist (located within a        pre-specified local area)    -   Geo-fence for system triggered specialist notifications to        visitors

Presence of specialist:

-   -   Getting a named specialist    -   Queuing a specialist specifically for more than one visitor at a        time. Each visitor may be serviced in order of service requests        received    -   Changing states of a specialist for specific work modes (e.g. in        meeting, unavailable, in-route to job, etc.)    -   Voice Callback of a visitor    -   Scheduling callbacks by visitors for specific business Ads in        the system

Data analysis:

-   -   Analysis of “Ad data” collected from the Ad service    -   Analysis of “survey” data collected by the (e.g. live connect        Ad) system    -   Analysis of both “ad data” and “survey” data combined    -   Analysis of “geo” and “presence” data collected by the system    -   Analysis of any data combination based on custom algorithms,        including an additional source of data from the business    -   Analysis of “NPS” data collected by the system

Social network

-   -   Visitor posting of a comment to a single social network of their        choice    -   Visitor posting of a comment to a single social network of the        businesses choice    -   Visitor posting of a comment to multiple social networks of        their choice    -   Visitor posting of a comment to multiple social networks of the        businesses choice    -   Visitor taking NPS satisfaction survey

Live connect button states

-   -   Button visibility if NO agents (or specialists) are “present” on        the system    -   Button visibility if NO agents are “available” even though they        are present on the system    -   Button image change based on specific visitor prequalification        value (e.g. an attribute value assigned for the specific        visitor)

Activities of live connect Ad services provided in system 153 may becaptured/logged in content activity DB 231. The logged activities mayindicate, for example, a history of requests received from external Adservers (or Ad networks), corresponding live connect Ads served, visitordata, live communications established and/or attempted between arecorded visitor and a specialist(s), job history, job statues, visitorcomments, or other applicable transaction data. Report module 239 maygenerate various reports based on or derived from data captured inlog/report DB 231. For example, history of live connect services may beanalyzed to reveal a variety of statistics related to a businessparticipating in a live connect Ad services. The statistics may includenumber of times or frequencies live Ads were served, number ofspecialists responded, number of live conversations/communicationsestablished, number of jobs completed, or other applicable servicecharacteristics etc.

As described above, live connect server 153 may be integrated orcommunicatively coupled to a server or a cluster of servers (e.g., cloudservers) representing a support center. In one embodiment, datacommunications and routing request logic may include a set of javascript code (or other applicable script code to be executed in a clientdevice) to enable communications to the support center. When executed,the logic can provide a button for the visitor to click to engage with aspecialist. The logic may communicate the necessary data from an Adsystem to the support center for analysis. The channel/skill specifiedin the code may be updated based on a response received back from thelive connect Ad service (e.g. based on the data analysis by the DAE 213)to change the route to a skilled specialist for a live communication tobe established for the specific visitor. The logic may communicate tothe support center the initiation (e.g. via the visitor) of a requestfor the associated channel and skill to establish the live communication(e.g. predominantly voice or chat).

Once a live communication session has been established, the supportcenter may collect or log interaction activities between the visitor,the specialists, and the live connect Ad system. This information can bestored into a database (e.g., database 231) for operational reportingand analysis of the efficiency of the live connect ad system. Thesupport center may perform data processing operations to enableinteractive advertisement activities, message routing, datacommunication and data collection during the course of the interaction.

Photos from the visitor can be taken (e.g. dynamically via the livecommunication link) and communicated to the specialist allowing a remoteview into the needs of the visitors issue. A specialist can thendetermine the scope of the job, the amount of work required to completethe job (e.g. short job or long job, one person or multiple-person job),whether the specialist/business has the exact expertise to perform thework or other characteristics/attributes of the job based on the visitorneeds and the business's capabilities. As a result, the job may beagreed or declined between the specialist and the visitor in real timevia the live communication link.

The live connect Ad service may work with Ad services to provide avariety of types of real time live connected advertisements. Forexample, a live connected advertisement may result from direct internet(or web) searches, landing pages of search results, landing pages ofmapping related search results, web navigation from rich mediaadvertisement (e.g. banner ads), video playing (e.g. video placementads), video overlaying, TV (television) connection, mobileconnections/navigations or other applicable advertisement triggeringopportunities.

The live connect Ad services may perform routing operations after a formof analysis is completed to determine a route to a skill/channel inorder to reach a specialist in support of visitors' needs based on liveconnect Ads clicked. The support center system of the live connect Adservices can support a number of routing or communications channels suchas traditional voice, IVR (interactive voice recording) voice,traditional chat, Facebook™ chat, Facebook™ posts, Twitter™ posts, SMS(short message service) messages, or other application real timecommunication links etc. An Ad network associated with the live connectAd services may set up advertising operations that leverage one or manyof these channels. Each channel can be setup to show or hide the buttona visitor would click based on availability of a specialist. The codebehind or embedded in the button (or other UI elements) may includeprocessing logic to communicate with the support center to determinesuch availability.

Referring back to FIG. 4, when an availability request for live contentis received from an Ad server (e.g., server 152) via interface module203, SME selection module 219 searches in SME DB 233 to identify a listof SMEs that are associated with the live content. For example, as shownin FIG. 5, SME selection module 219 examines table or data structure 251to determine a list of SMEs and based on the SMEs, presence engine 215and geolocation engine 217 determine whether the SMEs are online andtheir respective geographic locations. In one embodiment, based on theSME IDs, SME selection module 219 determines based on table or datastructure 252 the availability of each of the SMEs that are associatedwith the live content in question.

In one embodiment, the request for live content received from livecontent server 152 may include a content ID identifying a specific livecontent (e.g., media content or media documents), in this example, aspecific live connect Ad campaign. If there are multiple Ad campaignsassociated with a particular live content owner, the request may furtherinclude a client ID identifying that client. The request may furtherincludes certain user information of the visitor, such as a geographiclocation associated with the visitor, at which the requested servicewill be performed. Based on the content ID and/or client ID, SMEselection module 219 accesses a client account based on the client ID orcontent ID in client DB to identify a list of SMEs that are associatedwith the client and/or requested content. For each of the SMEs, the SMEselection module 219 accesses SME DB 233 to determine the states and/orstatus of the SMEs and to select the SMEs that are currently availableat the point in time.

Referring now to FIG. 5, which represents at least a portion of clientDB 234 as shown in FIG. 4. Specifically, data structure or table 251 mayrepresent a client account or entry of a particular client (e.g., a livecontent owner) maintained as part of client DB 234. In one embodiment,data structure 251 includes one or more entries, each corresponding to aspecific live content, in this example, a live connect Ad, which may beidentified by content ID 253. Content ID 253 may be received from livecontent server 152 when an administrator of the client provisioned livecontent, for example, creating a live connect Ad. Each entry may furtherincludes an optional group ID or name describing the live content, oneor more SME IDs 255 identifying the SMEs that have been associated withthe live content, ID 256 identifying an administrator, dispatcher, or anoverflow SME for the live content, terminology 257 defined for thatspecific live content, one or more rules 258 governing the live content,and communications methods or channels 259 (e.g., voice, chat, text,email, social networking) to be utilized for supporting the livecontent. Terminology 257 includes the terms defining the states andstatus of the associated SMEs, such as “available” and “unavailable.” Anexample of the terminology and rules is shown in FIG. 7B for a clientproviding plumbing services.

Note that the configuration as shown in FIG. 5 is described forillustration purposes only; other layouts, formats, and/or architecturesmay also be utilized. For example, data structure 251 may be indexed orsorted based on a client identifier identifying an owner or author oflive content. Data structure 251 may also be indexed or sorted basedcontent identifiers identifying the specific live content. Clientdatabase 234 represented by data structure 251 may further include aquery interface that allows a component to query based on differenttypes of query terms, such as, for example, client identifiers, contentidentifiers, etc.

Referring now to FIG. 6, which may be part of SME DB 233 and/or contentactivity DB 231, table or data structure 252 includes multiple entries.Each entry corresponds to an SME identified by SME ID 261. Each SMEentry further includes one or more live content IDs 262 that thecorresponding SME are associated with. For example, a single SME may beassociated with multiple Ad campaigns as shown in FIG. 7A. An SME entryfurther includes geographic location 263 of the SME, current job stateof the SME 264, current status of the SME 265, contact information ofthe SME 266, skill set of the SME 267, and other information such asuser preferences or a picture of the SME 268. Status 265 may be one of“available” and “unavailable.” Job state 264 may be one of “accepted,”“in process,” “on hold,” “transferred,” “canceled,” and “completed.”Note that the data structures as shown in FIG. 6 are described forillustration purpose only; other formats or layouts may also beimplemented. Furthermore data associated with the SMEs and/or livecontent may also be stored therein.

According to one embodiment, referring to FIGS. 5 and 6, live connectcontent interface module 203 of live connect server 153 receives arequest for availability information of SMEs associated with a livecontent. In response, availability module 211 is invoked to determine aclient ID and/or a content ID identifying the requested live content ofa particular client (e.g., a particular Ad of an Ad owner) from therequest, as well as other user information of a visitor. In oneembodiment, DAE 213 performs an analysis on the request, for example,determining the content ID and user information from the request. Geolocation engine 217 is to determine a geographic location associatedwith the visitor based on the analysis of the user information. SMEselection module 219 accesses client DB 234 to identify based on list ofone or more registered live content of the client based on the client IDand/or content.

Specifically, in one embodiment, SME selection module 219 identifies aclient account based on the client ID, for example, client account data251 as shown in FIG. 5. Based on content ID 253, SME selection module219 identifies a list of one or more SMEs 255. For each of theidentified SMEs 255, SME selection module 219 accesses SME DB 233 anddetermines the states 264 and/or status 265 of the identified SMEs (fromthe client account of FIG. 5), for example, based on SME IDs 261 asshown in FIG. 6. SME selection module 219 selects one or more SMEs thatare currently available at the point in time, where the availability ofthe SMEs may be determined by presence engine 215. SME selection module219 then transmits, via interface module 203, to live content server 251the SME information, such as, for example, SME information as shown inFIG. 9, including, but is not limited to, an indicator indicatingwhether an SME is currently available and the geographic location of theSME. Similarly, the configuration as shown in FIG. 6 is described forillustration purposes only; other layouts, formats, and/or architecturesmay also be utilized. Data structures 251 and 252 may be maintained in asingle database or multiple databases.

According to one embodiment, referring back to FIG. 4, the list ofavailable SMEs is transmitted to the Ad server via interface module 203.The Ad server (e.g., server 152) can then decide what live connect Adswill be presented to the visitors, for example, based on theavailability of the SMEs and other factors (e.g., geographic locationsof the available SMEs), which may be configured as part of rules orconfigurations at the Ad server. Subsequently, when the visitor clicks alive connect button of an Ad, a request is received at live connectserver 153, where the request includes identifying information of thevisitor (e.g., visitor's contact information). In response, live connectmodule 207 selects an available SME and informs live connect routingmodule 277 to route the visitor's information to a selected SME's clientdevice to allow the selected SME to establish a live communicationsession with the visitor, which can be a voice, text, video chat, socialforum etc. The availability of the communications methods or channelsmay be determined based on the client's settings and/or individual livecontent settings (e.g., settings 259 of FIG. 5), which may be the sameor different from one client to another client or from one live contentto another live content of the same client.

According to one embodiment, when a selected SME becomes unavailable orunwilling to accept a live connect request from the visitor, liveconnect routing module 227 routes the request to a pre-configuredoverflow SME, such as, one or more overflow SMEs specified in field 256of FIG. 5. There may be multiple overflow SMEs configured including, butare not limited to, a primary overflow SME and a secondary overflow SME.The overflow SME(s) 256 may be specified by an administrator of the livecontent and stored in the corresponding client account 251 of client DB234. In addition, SME management module 223 may automatically set thestate of the SME from “available” to “unavailable.” Alternatively, inresponse to a rejection from the assigned SME, the request may be routedto a preconfigured administrator (or dispatcher, manager). Theadministrator then dispatch the request to another SME who is availableand willing to accept the request. The administrator can also accept therequest, operating as an SME. The rerouting of the request may beperformed according to a specific set of rules (e.g., rules 258)associated with that specific live content owner. Note that any of thecomponents as shown in FIG. 4 can be implemented as logic in software,hardware, or a combination thereof. The content activity database 231,SME database 233, and client database 234 may be maintained in apersistent storage device such as a hard drive. Data stored in thesedatabases can be loaded by a processor into a memory to be accessed byother components as shown in FIG. 4.

FIG. 8 is a block diagram illustrating an example of live content serveraccording to one embodiment of the invention. In one embodiment, livecontent server 152 includes content service module 303 providing remoteservices for client devices, such as device 109 of FIG. 1. Contentservice module 303 can include a search engine, a gaming engine orsocial networking engine or other content/data processing components tooffer free or subscribed services to client devices. Content servicemodule 303 may be capable of serving advertisements (or ads) along withthe services via advertisement handler module 305.

In one embodiment, content processing module 305 can identify a list ofpossible live content, in this embodiment, advertisements (e.g.identified by advertiser identifiers) from content DB 307 based onclient data extracted from client service requests (e.g. a search term,geo location, network address, etc.) One or more of the possibleadvertisements may be registered with live connect capability (e.g. liveconnect advertisers) in the content DB 307, for the purpose ofillustration, an advertisement DB. Live connect module 309 can determineor select which of the identified live connect advertisements arecurrently available to offer live connect Ads according to the liveconnect capability.

For example, live availability service module 311 can determine locallyor remotely “availability” states of specialists associated with theidentified live connect advertisers. In some embodiments, liveavailability service module 311 may be notified (e.g. pushed), forexample, from a remote or locally coupled live connect service, withchanges of availability states of specialists related to live connectadvertisers registered in advertisements DB 307. The information of thespecialists may be stored and/or cached in SME or agent database 320from SME agent database 233 of live connect server 153 of FIG. 4. Liveconnect module 309 can select a number of the identified live connectadvertisements who are currently available (e.g. having specialists with“available” states) for content processing module 305.

Live content generation module 313 can generate or retrieve live connectAd content for selected live connect advertisers. Live connect Adcontent may include, for example, a live connect button or otherapplicable user interface element indicating to a visitor that a liveperson is available to offer a service in real time. Live connect Adcontent may include instructions (e.g. script code or other applicableprocessing specifications) embedded with a user interface element (e.g.a button) to be executed in a client device when activated by useractions to cause establishment of live connections between, for example,the client device and devices used by specialists with “available”states. In some embodiment, the embedded instructions may cause theclient device to notify (send requests to) the content presentationserver to refresh, for example, the live connect Ad content after aspecified time period (e.g. 20 seconds or other applicable time outperiod). Changes of availability states of related specialists mayupdate the user interface elements of the live connect Ad. For example,if the specialists are no longer available, the live connect button maybe removed or disabled from the live connect Ad displayed in the clientdevice in real time.

According to another embodiment, an administrator of a company mayconfigure or set up an Ad a configuration user interface (e.g., Webinterface), not shown. The administrator may utilize standard Adtemplates provided by live content server 152 and the Ads are stored incontent database 307. In response to a request received from a contentpresentation server (e.g., Yahoo or Google search engine), contentprocessing module 305 searches in content DB based on the informationobtained from the request (e.g., search term) to identify one or morelive Ads that have been previously registered with server 152. Anintelligent analysis may be performed to identify the related Ads. Foreach of the identified Ads, live availability service module 311communicate with another server, i.e., live connect server 153, toobtain a list of zero or more SMEs that are available at the point intime, including their respective geographic locations. Based on theavailable SMEs, the live Ads are then transmitted to the visitors,optionally via the content presentation server.

According to one embodiment, availability service module 311 transmits aquery to live connect server 153 to inquire whether a particular contentor Ad has at least one SME currently available. The definition of“available” refers to an SME has logged into the live connect server andset its status “available.” Merely logging into the live connect serveronly indicates that the SME is presence, not necessarily available. Inone embodiment, the query message may include one or more Ad IDsrepresenting the live Ads that have been registered and found in livecontent DB 307. In response, live connect server 153 identifies a listof zero or more SMEs for each of the Ads being queried and return aresult back to live content server 152.

According to one embodiment, as shown in FIG. 9, the returned message ordata packet includes one or more segments or data structurescorresponding to the one or more Ads being query. Each data structureincludes one of the Ad ID (e.g., Ad ID 351) identifying a correspondingAd and an indication (e.g., indication 352) indicating whether the Ad isavailable or alive. If the corresponding Ad is available or alive, thedata structure also includes a list of one or more SMEs that have beenconfigured and associated with the Ad. Each SME in the list includes anSME ID (e.g., SME IDs 353-355) identifying the corresponding SME, anindication (e.g., indications 356-358) indicating whether the SME isavailable, and geographic location information of the SME. Thegeographic location of an SME may be presented by longitude data andlatitude data that are compatible with GPS data. For each of the Adsthat is available or live (e.g., with at least one available SME), thereturn information further includes a communication link for each of thecommunication methods (e.g., text, voice links 359-360) and a map link(e.g., map link 361) linking with a geographic location of the Ad. Forexample, if the Ad supports both text and voice communication methods,there will be two links presented, one for each of the methods. The linkor links include embedded therein executable code and to be associatedwith a live connect button or buttons (e.g., buttons or controls 613-614of FIG. 15B) to allow a visitor to contact the live connect server inreal time when the corresponding Ad is presented. In this example asshown in FIG. 9, SMEs “1234” and “1235” are available and SME “1236” isunavailable. Note that if an Ad is indicated as unavailable, the list ofSME may not be provided by the live connect server. According to oneembodiment, live connect server 153 may periodically send or pushupdated availability information to live content server 152 to be cachedin SME DB 320, using the similar protocols or data structures as shownin FIG. 9. Furthermore, the detailed information of the specialists mayalso be periodically synchronized between live content server 152 andlive connect server 153.

According to one embodiment, live content server 152 further includescontent provisioning module 315 to provision or configure live contentstored in live content database or store 307. Provisioning module 315may provide a content provisioning interface (not shown) to allow acontent owner or administrator to provision live content. For example, auser may create a live content account stored in live content database307 and provision one or more live content, such as, for example, liveconnect Ads. The user may use a live content template such as an Adtemplate to create a live connect Ad. An example of Ad templates areshown in FIGS. 15A-15C. Once the live content has been provisioned andstored in content database 307, content provisioning module 315transmits the identifying information (e.g., a live content ID) of thelive content to live connect server 153 of FIG. 4 to be populated orincorporated into a live connect account associated with the livecontent owner. As a result, the live content account maintained in livecontent server 152 is linked with a live connect account maintained inlive connect server 153.

According to one embodiment, live content server 152, as an Ad server,may be communicatively coupled, for example, via a set of agreed uponapplication programming interfaces (APIs) or protocols, to a specific Adnetwork, being one of the Ad server members of the Ad network.Alternatively, according to an alternative embodiment, live contentserver 152 may be communicatively coupled to multiple Ad networks, forexample, using multiple Ad network interfaces (not shown), eachcorresponding to one of the Ad networks, such as, for example, Yahoo,Google, Microsoft Bing, etc. According to a further embodiment, theremay multiple live content servers, one for each of the supported Adnetworks, communicatively coupled to the live connect server 153.

An Ad network represents an entity that connects advertisers to Websites that want to host advertisements. The key function of an Adnetwork is aggregation of Ad space supply from publishers and matchingit with advertiser demand. The phrase “Ad network” by itself ismedia-neutral in the sense that there can be a “Television Ad Network”or a “Print Ad Network”, but is increasingly used to mean “online adnetwork” as the effect of aggregation of publisher ad space and sale toadvertisers is most commonly seen in the online space. An Ad server is acomputer server, specifically a Web server backed by a database server,that stores advertisements used in online marketing and delivers them towebsite visitors. The content of the webserver is constantly updated sothat the website or webpage on which the ads are displayed contains newadvertisements—e.g., banners (static images/animations) or text—when thesite or page is visited or refreshed by a user. The purpose of Adserving is to deliver Ads to users, to manage a websites advertisingspace and (in the case of advertiser Ad servers) to provide anindependent counting and tracking system for advertisers.

Note that any of the components as shown in FIG. 8 can be implemented aslogic in software, hardware, or a combination thereof. Live content DB307 and cached SME DB 320 may be stored in a persistent storage devicesuch as a hard drive. Data stored in these databases can be loaded by aprocessor into a memory to be accessed by other components as shown inFIG. 8. Also note that although a live connect Ad is utilized as anexample of live content throughout this application, however, it will beappreciated that the techniques described throughout this applicationcan also be applied to other types of content, such as, for example,media content, media presentation, or media documents, etc.

FIG. 10 is a process diagram illustrating sample transactions toestablish communication links for live connect Ads according to oneembodiment of the invention. Sequence 400 may be implemented based onsome components of the system of FIG. 4 or the system of FIG. 8. In oneembodiment, at transaction 413, client device 401 may send a searchrequest including the terms, such as “Plumber Now,” to web server 403.Device 401, such as device 109 of FIG. 1, may be used by a visitor toaccess remote services, such as web search service of content/dataservice 105 of FIG. 1, offered by web server 403. In response, attransaction 415, web server 403 may request sponsored ads from Ad server405 passing along visitor data including, for example, the search terms.Ad server 405 may look for or request relevant Ads via Ad network 407 attransaction 417 based on visitor data passed from Web server 403. Adserver 405 and Ad network 407 may be implemented as part of live contentserver 152. In response, Ad network 407 can identify a list of candidateAds as requested from Ad server 405. A portion of the candidate Adsidentified may be registered as live connect Ads.

In one embodiment, at transaction 419, Ad network 407 can request LCAserver 409 to determine which of the live connect Ads are live (e.g.,there is at least one SME currently available). For example, Ad network407 can forward a list of identifiers of the candidate live connect Adsto LCA server 409 for providing a specified number (e.g. 2 or othernumber) of live connect ads which are currently available. LCA server409 may provide live connect service, such as live connect service 103of FIG. 1. Ad network server 407 may pass visitor related data, such asgeo locations, urgency, schedule or other applicable data to LCA server409 to identify availability of live connect ads.

Specialists may have availability states timely updated with LCA server409 to indicate whether they are currently available for live connectservices. For example, a change of state from “unavailable” to“available” of a specialist (SME) may be notified from SME or agentdevice 411, such as device 113 of FIG. 1, used by the specialist to LCAserver 409 at transaction 421. Accordingly, LCA server 409 can maintainan up-to-date state for the specialist for possible participation inlive connect Ads service.

At transaction 423, in one embodiment, LCA server may analyze datareceived from Ad network 407 to determine current availability of a listof candidate live connect Ads. LCA server may query currently availableSMEs (e.g. based on availability states) and match geo locations toidentify available SMEs based on visitor data received. At transaction425, the identified SMEs may be returned to Ad Network 407. In turn, AdNetwork 407 can forward identified SMEs as selected live connect Ads andother applicable data to Ad Server 405 at transaction 427. Attransaction 431, Ad sever 405 can send packaged data (e.g. for creatingAd content) with availability info as part of Ad content (e.g. liveconnect Ads) to client device 401 via web server 403.

The visitor may select live connect Ads presented in a returned searchresult, for example, by clicking on a live connect button in the liveconnect Ads. Embedded code in the live connect button may be executed inclient device 401 to exchange messages with LCA sever 409. Attransaction 429, client device 401 may present a user interface (UI)prompt for user contact information (e.g. phone number, address or othervisitor data). The visitor may fill out the contact information for amobile browser of client device 401 to send out service requests to LCAserver 409 at transaction 433.

LCA server 409 may identify and/or select available SMEs (e.g. SMEscurrently available for establishing live connections) and send servicemessages to SME device 411 (e.g. via a mobile application for liveconnect Ad services) used by the selected SMEs at transaction 435. SMEdevice 411 may receive user interface actions from SMEs to accept theservice request at transaction 437. For example, SMEs may click on “callnow” button to accept the service request. In one embodiment, SME device411 may notify LCA server 409 changes of availability state of the SME(e.g. becoming “unavailable”) at transaction 439. A live communicationsession may be established between SME device 411 and client device 401at transaction 441. The live communication session may be establishedbased on existing communication networks (e.g. phone network, messagingnetwork etc.) out of band from advertisement connections sending liveconnect Ads. Alternatively or optionally, the live communication sessionmay be established based on connections established for serving liveconnect Ads (e.g. in band).

The visitor and the SME may converse to determine if the SME willreceive the work or not. The visitor may decide to contract the SME andthe SME heads to the visitor's location. The live communication link(e.g. a call) between the visitor and the SME may then be disconnected.At transaction 443, messages may be sent from SME device 411 to LCAserver 409 to update service status or job status (e.g. “in progress”,“complete”, “on job” etc.) for the job requested by the visitor via liveconnect Ads. At transaction 445, in one embodiment, after the job iscompleted, a notification may be sent from SME device 411 to LCA sever409 for a state change of the SME to become available again forreceiving additional service requests.

FIG. 11 is a sequence diagram illustrating sample transactions toprovision a service provider for live connect Ad services according toone embodiment of the invention. In one embodiment, at transaction 453,service admin server (e.g. LCA server) 451 sends an email or otherapplicable notifications with registration instructions to a specialistusing SME device 452 to participate in live connect Ad campaign.Registration instructions may include a registration token or codedynamically generated for secure authorization purposes. At transaction454, a mobile application for the live connect Ad service may bedownloaded and installed in SME device 452. For example, theregistration instructions received by the specialist may include a linkto download the mobile application from a remote server, such as serviceadmin server 451 or other applicable servers for the live connect Adservice. At transaction 455, SME device 452 sends a registration noticevia the mobile application to service admin server 451 to request toparticipate in the live connect Ad campaign. The registration notice mayinclude a registration token or code previously received by thespecialist. At transaction 456, SME device 452 may indicate a defaultavailability state of the specialist as “pending approval” toparticipate in the live connect Ad campaign.

At transaction 457, in one embodiment, in response to an approval of anadministrator, service admin server 451 may send an approval message toSME device 452 to approve participation of the specialist, for example,via the mobile application, to the live connect Ad campaign or service.The mobile application may allow change of states of the specialistafter receiving the approval from service admin server 451. Attransaction 458, SME device 452 may send a message (e.g. in response toUI instructions received from the specialist) to service admin server451 to update availability state of the specialist as “available” toparticipate in the live connect Ads service. The message may includeauthentication data such as login/password to authenticate thespecialist in service admin server 451.

FIG. 12 is a sequence diagram illustrating sample transactions toguarantee live communications for live connect Ad services via anoverflow provider according to one embodiment of the invention. In oneembodiment, at transaction 469, client device 461, such as client device109 of FIG. 1, of a visitor, may send a service (e.g. live connectservice) request via a live ads presented on client device 461. Forexample, the visitor may click a live connect button of the live ads toissue the service request. In one embodiment, LCA server 463 canidentify currently (when requests are received) available specialistsfor the live connect service requested from client device 461. Aspecialist associated with SME device 465 may be selected for the liveconnect service request. At transaction 471, LCA server 463 sendsservice messages and/or visitor related data to SME device 465 to notifythe specialist. The visitor related data may be extracted or derivedfrom the received service requests. LCA server 463 may start a timer toensure that the selected specialist responds to the service requestwithin a certain period of time (e.g. predefined short period withliveliness).

At transaction 473, in one embodiment, LCA server 463 detects timeoutwaiting for an indication that the selected specialist associated withSME device 465 has responded to the service messages. The indication mayinclude, for example, a state change notification from SME device 465 tomake the specialist unavailable for new service requests. LCA server 463may automatically set (or force) a change of availability state of thespecialist to become “unavailable” when no response was received withina certain period of time for the timeout. A specialist with the“unavailable” state may not be selected to provide live connectservices. At transaction 477, LCA server 463 reroutes service messagesreceived from client device 451 to an overflow SME device used by anoverflow specialist designated to provide live service as needed (e.g.when a selected specialist fails to respond to service requests orcannot be contacted in real time). A notice of acceptance to the servicerequests may be sent out from overflow SME device via the overflowspecialist. As a result, live communication link 481 may be establishedbetween client device 461 and overflow SME device 467 even when anoriginally selected specialist is not available and/or when no availablespecialists can be identified.

FIG. 13 is a flow diagram illustrating a method for providing liveconnect services according to one embodiment of the invention. Method500 may be performed by processing logic which may include software,hardware, or a combination thereof. For example, method 500 may beperformed by live connect server 153 of FIG. 2. Referring to FIG. 13, atblock 501, processing logic receives at a first server (e.g., liveconnect server) from a second server (e.g., live content server) over anetwork a first request of a first user for communicating with anotheruser (e.g., agent) concerning a content item of a presentation (e.g.,live connect Ad) presented by the second server. The first user accessesthe presentation provided by the second server, for example, via acontent presentation server (e.g., Web server with search engine orsocial Web site). The request may further includes a content ID thatidentifies the content item presented by the second server (e.g., Ad IDidentifying a live connect Ad). The content ID may be provided by thesecond server by identifying a live content based on user interactionwith the content server. The request may further include userinformation of the first user, such as, for example, geographic locationof the first user. At block 502, in response to the first request,processing logic identifies from a database (e.g., client database) oneor more users, agents, or specialists that are associated with thecontent item, for example, based on the content ID. The database storesagents or specialists that have been configured and associated withvarious content items identified by the respective content IDs.

At block 503, processing logic determines the status of each of theidentified users or agents, including determining whether each of theusers or agents is available to communicate with the first user todiscuss the content item at the point in time. Processing logic mayfurther determine a geographic location for each of the users orspecialists that are available. If there is at least one user or agentthat is available for the content item, at block 504, processing logicsends availability information to the second server for such anindication, optionally including a geographic location of at least oneavailable user or agent. Alternatively, a list of user or agent IDsidentifying available users or agents may be transmitted from the firstserver to the second server, optionally including their respectivegeographic locations. At block 505, a second request is received fromthe second server or from a client device of the first user forcontacting an available user or agent that is associated with thecontent item. The second request may include a content ID identifyingthe content item and contact information of the first user. In responseto the second request, at block 506, processing logic transmits amessage to a second client device or agent device of a second user oragent that is associated with the content item and is available. Themessage includes contact information of the first user to allow thesecond user or agent to establish a live communication session with thefirst user.

FIG. 14 is a flow diagram illustrating a method for providing liveconnect services according to another embodiment of the invention.Method 550 may be performed by processing logic which may includesoftware, hardware, or a combination thereof. For example, method 550may be performed by live content server 152 and/or content presentationserver 151 of FIG. 2. Referring to FIG. 14, at block 551, a firstrequest is received at a first server (e.g., live content server 152)from a first user device of a first user via a graphical user interfacemaintained by the first server. The first request requests searchingcontent or media content documents (e.g., live connect Ad) associatedwith a search term specified in the first request. In response to thefirst request, at block 552, processing logic searches in a contentdatabase (e.g., live content database or live Ad database) to identify alist of media content documents (e.g., live content documents or liveAds) based on the search term. Each of the media content documentscontains description related to the search term.

At block 553, for each of the identified media content documents,processing logic determines a document ID at block 554, transmits thedocument ID to a second server over a network at block 555, and receivesan indication from the second server indicating whether there is atleast one agent or specialist currently available for providing livesupport for the media content document at block 556. Alternatively, alist of zero or more available agents or specialist is received from thesecond server, as well as their respective geographic locations. Atblock 557, one or more of the identified media content documents thathave at least one available agent or specialist are presented to thefirst user device of the first user. Each of the media content documentsis represented with at least one geographic location of the agent orspecialist and a live connect button or control to reach the agent orspecialist.

FIGS. 15A-15C are screenshots illustrating an example of a graphicaluser interface for providing live content according to some embodimentsof the invention. The graphical user interface (GUI) as shown in FIGS.15A-15C may be presented by content server 151 and/or live contentserver 152 of FIG. 2 and displayed at a client device of a visitor orend user. Referring to FIG. 15A, in this example, a visitor has visiteda content server (e.g., content presentation server 151) and typed in asearch term “plumber now” in search field 601. In response to the searchterm, in addition to search and find static content 602, the server maycommunicate with a live content server (e.g., live content server 152)to obtain a list of live content that is associated with the searchterm. In addition to sending the search term to the live content server,the content presentation server may send user information of the visitorto the live content server, such as, for example, a geographic locationof the visitor. The geographic location of the visitor may be obtainedusing a location service, which may be implemented locally or via athird-party service. For example, the geographic location of the visitormay be obtained based on its Internet protocol (IP) address (e.g., via acorresponding Internet service provider) or global positioning system(GPS) data obtained from its mobile device.

As described above, the live content server may perform an analysis onthe search term, as well as the user data, to identify a list of livecontent that has been registered with the live content server. For eachof the live content, the live content server sends a query to a liveconnect server (e.g., live connect server 153) to obtain theavailability information of the live content. The live connect serverdetermines zero to more specialists for each live content that arecurrently available and turns a signal for such an indication to thelive content. Based on the availability information received from thelive connect server, the live content server determines a list of livecontent to be sent to the content presentation server. For example, thelive content server may decide (e.g., based on a set of rules configuredby the live content owner) that only the live content that have at leastone available specialist will be sent to the content presentation serverto be presented to the visitor.

Referring back to FIG. 15A, in this example, it is assumed live Ads 603are received from the live content server that has at least onespecialist available. Furthermore, the geographic locations of the liveAds 603 are also shown in a map 604. In one embodiment, only the liveAds having at least one available specialist within a geographicproximity of the visitor are presented, which may be configured orspecified by the Ad owners and/or the visitor. The visitor can selectany of the displayed Ads 604 to evaluate the detailed information of theAds. Referring now to FIG. 15B, it is assumed the visitor has selectedAd 611. In response to the user selection, the detailed information ofthe selected Ad is displayed in display area 612, including somepictures of the service or product provider associated with the selectedAd and a map showing its geographic location (e.g., geographic locationsof its headquarter or specialists). The detailed information may beretrieved from the live content server in response to the userselection. For example, in response to the user selection, the contentpresentation server may send a request to the live content server toobtain the detailed information of the Ad. The live content server inturn sends a request to the live connect server to obtain the currentgeographic locations of the associated specialists.

In addition, according to one embodiment, one or more live connectbuttons 613-614 are displayed for the selected live Ad. In this example,the visitor can click a live connect button 613 to initiate a chatsession with an available specialist or click a live connect button 614to initiate a voice conversation with an available specialist. Note thatthe live connect buttons 613-614 may only be displayed or enabled ifthere is at least one specialist available for that particularcommunication method (e.g., SMS or voice call). Otherwise, thecorresponding live connect button may not be displayed or enabled. Inone embodiment, some Ads may be defined to allow for either a voicecommunication or a chat communication, typically both will not beutilized together. This is defined by the business in which the Ad isdisplayed for.

In response to the activation of a live connect button, the visitor maybe prompted for further user information as shown in FIG. 15C. Referringto FIG. 15C, the visitor is prompted via a dialog box 615 to entercontact information of the visitor, such as its phone number and addressthat a service will be performed. The user information is thentransmitted to the live connect server in response to the send button indialog box 615. The send button may include underlying executable codethat in response to the activation of the send button, sends the userinformation to the live connect server. The live connect server thenselects and distributes the user information to one of the availablespecialist to allow the selected specialist to contact the visitor for alive conversation. Note that the Ads displayed in FIGS. 15A-15C may bereceived directly from the live content server 152 or alternatively,from content presentation server 151.

According to one embodiment, in order for an SME to provide live supportservices to a visitor or customer of live content, the SME has toregister with live connect server 153 and/or live content server 152.Theregistration of the SMEs can be done via a registration interface oflive connect server 153 and/or live content server 152. In oneembodiment, an administrator of an Ad owner or a company that providesproducts and/or services being advertised can set up and configure oneor more SME for an Ad campaign. As described above and shown in FIGS. 5and 6, a service or product provider can have multiple Ad campaigns andan SME can be associated with one or more Ad campaigns.

In one embodiment, an administrator can specify the specialists for eachAd campaign, including the contact information of the specialists in aspecialist database such as SME or agent database 233 as shown in FIG.5. Each of the specialists has to install a specialist mobileapplication onto its mobile device and log into the live connect serverfrom the mobile application in order to communicate with the liveconnect server, such as registration, receiving notification, settingstatus of the specialist, etc.

According to one embodiment, during the registration of the SMEs, anadministrator sends emails or other applicable notifications withregistration instructions to mobile devices of the SMEs to invite themto participate in live connect Ad campaign. Registration instructionsmay include a registration token or code dynamically generated forsecure authorization purposes. In response to the notification, an SMEmay download a mobile application for the live connect Ad service andinstall in the SME device. For example, the registration instructionsreceived by the specialist may include a link to download the mobileapplication from a remote server specified in the link. The SME devicemay send registration notice via the mobile application to the liveconnect server to authorize a request to participate in the live connectAd campaign. The registration notice may include registration token orcode previously received by the specialist. In one embodiment, inresponse to an approval of an administrator, the administrator may sendan approval message to the SME device to approve participation of thespecialist, for example, via the mobile application, to the live connectAd campaign or service. Thereafter, the SME can indicate whether he/sheis available by changing the status through the mobile application,where the status is stored as part of SME or agent database as shown inFIG. 5.

According to one embodiment, the status of the SMEs can be utilized bylive connect routing module 227 to determine whether an incoming contactrequest should be routed to the respective SME. For example, a requestmay only be routed to an SME that has an “available” status. The liveconnect routing module can automatically select and route an incomingrequest to any of the available SMEs. An SME can accept or deny anincoming request through its mobile application. If none of the SMEs isavailable or willing to accept an incoming request, the live connectrouting module can route the request to a predetermined or preconfiguredoverflow SME, dispatch person, or a manager/administrator, such that thevisitor will be guaranteed to talk to a live person.

FIGS. 16A-16J are screenshots illustrating an example of graphical userinterfaces of a mobile application utilized by a specialist according tosome embodiments of the invention. For example, the GUIs as shown inFIGS. 16A-16J may be presented by client application 182 of clientdevice 155 of FIG. 2. Referring to FIG. 16A, in this example, assumingthe corresponding SME has its status set to “available,” when anincoming request is received at the live connect server, the routingmodule is to select and send a job offer to an SME that is available forthat Ad for a client, the channel and the skill In this example as shownin FIG. 16A, the GUI displays a message from the live connect server,including a brief description of the job offer. The SME can decline theoffer by clicking a decline button, which may lead to a history page asshown FIG. 16D indicating that the SME has declined that particularoffer, including the date and time of the decline. In addition,according to one embodiment, the SME's status is automatically changedto “unavailable.” Since the SME declines the job offer, the system mayconsider that the SME is unavailable. However, the SME can manually setits status back to “available” or other statuses.

From the GUI page of FIG. 16A, the SME can accept the job offer bydirectly clicking a button to contact the customer, in this example, acall now button, which may lead to the GUI page as shown in FIG. 16C. Inaddition, the SME can clicks the view detail button which the GUIdisplays the detailed information of the job offer as shown in FIG. 16B.The detailed information may include the name of the potential customer,brief description of the job, contact information (in this example, aphone number), and an address of the potential customer. From thedetailed information page, the SME can also decline or accept the joboffer by clicking the respective buttons. In one embodiment, if the SMEaccepts the job offer, the application may automatically set the statusof the SME as “unavailable” as shown in FIG. 16B, which will betransmitted back to the live connect server and stored in the SME oragent database 233 therein. The rationale behind it is that since theSME has accepted one job, it may take a while to complete the job andthe SME is not able to accept another job. From the GUI page as shown inFIG. 16B, the SME can click the contact information (in this example, aphone number) to directly contact the customer. The SME can also clickon the address to view geographic location of the job site, for example,before accepting the job.

According to one embodiment, a job offer may be received from a dispatchor administrator instead of automatic routing by the routing module asshown in FIGS. 16E-16G. In this embodiment, a visitor may directly clickthe phone number shown in a live Ad, which is routed to a dispatchperson or an administrator's device. The dispatcher can talk to thecustomer and then select and route a job offer to a selected SME asshown in FIG. 16E. Similar to the situation as shown in FIGS. 16A-16D,the selected SME can decline the job offer as shown in FIG. 16G or viewthe details of the job as shown in FIG. 16F. An SME can also set itsstatus via the client application as shown in FIGS. 16H-16J, where theupdated status information will be transmitted from the clientapplication back to the live connect server to be stored in the SME oragent database.

FIGS. 17-18 are process diagrams illustrating interactions between thelive connect server and a client application of a specialist accordingto some embodiments of the invention. Referring to FIG. 17, in thisexample, after an SME launches the client application and logs into thelive connect server at block 801, the SME can set or change its statusvia the client application at block 802, which can be available status803 or unavailable status 804. If the status of the SME is set to“available” the SME can receive any incoming offer at block 805,including the contact information of the visitor of the Ad. The SME caneither accept the job offer at block 806 or decline the offer at block807. If the offer has been declined, the incoming request will be routedto another SME, an overflow SME, or a dispatcher at block 810, and itsstatus may be automatically changed to “unavailable” at block 809. Oncethe SME accepts the offer, the SME can directly contact the potentialcustomer for negotiate a service contract with the Ad visitor. If theSME reaches an agreement with the Ad visitor, the SME may change itsstatus from “available” to another status such as “in process,” and oncethe job has been completed, its status can be changed to “job completed”or back to “available.” If the SME cannot reach a service agreement withthe potential customer, he/she can decline the request and its statusmay be changed back to “available.”

Referring now to FIG. 18, in this example, an incoming offer is receivedfrom a dispatcher. After the SME successfully logs into the live connectserver, the SME can set or change its status, such as “available” statusat block 851 or “unavailable” status at block 852, manually orautomatically by the client application. For example, an SME canconfigure the client application to set its status to “available” bydefault once the SME logs in. The SME's status is updated at the SME oragent database at the live connect server and “seen” by the dispatcher.As a result, when an incoming query is received from the customer, thedispatcher can assign the offer to an SME that becomes available. Whenthe SME receives the dispatched message from a dispatcher, at block 853,the SME can contact the customer to negotiate a service contract andonce the agreement is reached at block 854, the SME can perform the joband its status is properly set. The SME can also decline the job atblock 855 after contacting the customer, in which case, the message isrouted back to the dispatcher.

FIGS. 19A-19H are screenshots illustrating an example of a managementuser interface for managing users according to one embodiment of theinvention. The GUIs as shown in FIGS. 19A-19H may be provided by a livecontent server and/or a live connect server as described above anddisplayed at a client application of an administrator or dispatcher of alive Ad owner (e.g., client device 156 of FIG. 2). Referring to FIG.19A, which is a home page of the management interface, the GUI pageincludes several page selectors or tabs representing dashboard page 901,manage users page 902, groups page 903, dispatch page 904, reportingpage 905, and business setting page 906. These pages can be displayed byclicking the corresponding page selectors or tabs 901-906.

Referring to FIG. 19A, the GUI page represents dashboard 901 as a homepage. From the home page a user (e.g., administrator) can accesses adispatch center from display area 907 to manage and dispatch incoming orqueued service requests received from the live Ads to proper SMEs thatare available. The user can also access SME management system fromdisplay area 908, for example, for managing the SMEs and inviting newSMEs to participate a live Ad campaign.

FIG. 19B shows an example of a page for managing users, which can beactivated by selecting tab 903 from FIG. 19A. From FIG. 19B, theadministrator can manage the SMEs that are associated with the owner ofone or more Ad campaigns. The administrator can create a new user as anSME by clicking button 911 and send out an invitation code to apotential new user via button 912. The administrator can create a newuser by specifying the name and contact information (e.g., phone and/oremail address) of the new user. In addition, the administrator canassociate the new user or any of the existing users to a particulargroup representing a particular Ad campaign. As described above, a usercan be associated with multiple groups or Ad campaigns. A photo of thenew user can also be uploaded into the system, such that when the usercontacts a customer, its photo can be sent to the customer for securityreason. The customer can expect the same person to come to his/herpremises to perform the job. An invite code can also be sent to the newuser, for example, via email or text, as a link to allow the new user toactivate the link for registration. From the GUI, the administrator cangenerate a new invite code, which may be associated with that particularcompany or a particular one of the Ad campaigns associated with aparticular company. The invite code may be valid for a particular periodof time for security reasons during which the new user has to respond.

In addition, the administrator can display some or all of the users thatare have been registered with the system. The users can be identified bysearching based on a variety of categories, such as group or Ad campaignname. If there is a new user that is pending for approval, an approvebutton 914 will be displayed next to the corresponding new user. Forexample, if the administrator has sent (e.g., email or text) out aninvite code to a new user via button 912 after entering all of thecontact information of the new user via button 911, the new user mayhave received the invite code and registered with the system. That willrequire the final approval from the administrator after theadministrator verifies the new user. The administrator can simply clickthe approve button to complete the registration of the new user. FromFIG. 19B, the administrator can view the detailed contact information ofthe users, status of the users, recent activities of the users, andmarket sector or geographic location of the users. The administrator canalso select any one of the displayed users to display further detailedinformation of the selected user.

FIG. 19C shows a user interface for group management, where the GUI pagecan be displayed by clicking tab 903 from any of FIGS. 19A-19B.Referring to FIG. 19C, from the group management page, an administratorcan create a new group or manage an existing group. The administratorcan configure settings of a group via link 921. The administrator cancreate a new group or configure an existing group by specifying a nameof the group and a brief description of the group. The administrator canalso specify a geographic location or territory (e.g., market sector) ofa group via link 922. For example, the administrator can provide anaddress or a zip code which mapped to a specific location of a map,using a location or map service. The administrator can also specify adefault map zone level, such that a preconfigured zone level of a map isdisplayed when a customer selects the corresponding Ad campaign (e.g.,FIG. 15A). According to one embodiment, the administrator can alsoselect and associate one or more users or SMEs with a particular group(e.g., Ad campaign) via link 923. From users page 923, the administratorcan specify detailed information of the users, including a name, role(e.g., technician), and contact information of the users. Theadministrator can also send an invite code to invite a new user to joina particular group via link 924.

FIG. 19D shows a GUI page for dispatching incoming requests to one ofthe available SMEs of a particular Ad campaign. An administrator can loginto a dispatch center for a particular group or Ad campaign. In thisexample, referring to FIG. 19D, it is assumed the administrator haslogged into the dispatch center via a management interface of a liveconnect server. During the log in, according to one embodiment, theadministrator may have to specify which of the Ads he/she wants todispatch. In this example, as shown in FIG. 19D, there is an incomingjob request that is received at the dispatch center. The detailedinformation of the job request is displayed in display area 931,including contact information, in this example, a phone number, of thecustomer and an address of the job site. The administrator can chatcommunicate, in this example, chatting, with the customer to obtaininitial information of the requested job. The administrator can declinethe job request or accept and dispatch the job request to one of theavailable SMEs displayed in display area 933. In this example, displayarea 933 may display all of the SMEs that are associated with the Adcampaign from the job request received. The statuses of the SMEs arealso displayed. The administrator can select one of the SMEs from 933,which will display a geographic location of the selected SME withrespect to the geographic location of the job site (e.g., geo fence) ina map, as well as other information of the selected SME in display area934. From the detailed information of a selected SME in display area934, the administrator can assign the job request to the selected SME.In response to the assignment, the live connect server routes therequest to a client device of the selected SME.

FIG. 19E shows a GUI for setting or configuration, which may bedisplayed in response to an activation of tab 906 of FIGS. 19A-19D. Fromthe setting page as shown in FIG. 19E, an administrator can set up anoverflow SME by providing contact information and/or communicationmethod, such as a phone number or email address, and a default action ifno regular SMEs are available or a previously selected SME declined thejob offer. The default action can be forwarding to a preconfiguredoverflow SME or forwarding to another SME that is available. FIG. 19Fshows an example of GUI that allows the administrator to defineterminology specifically for a particular Ad campaign or a specificcompany. FIG. 19G shows an example of GUI to allow the administrator toset up certain available status, while FIG. 19H shows an example of GUIto allow the administrator to define customized states. Note that theGUIs as shown in FIGS. 19A-19H may be generated and received from liveconnect server 153 and/or live content server 152 and presented at aclient device of an administrator 156 of FIG. 2, when an administratorlog in from its client device. The user interaction with the GUIs asshown in FIGS. 19A-19H may be captured and transmitted from the clientdevice back to the servers 152-153 or vice versa, for example, handledby SME management module 223, rule engine 225 of live connect server153. Live content server 152 and live connect server 153 mayperiodically communicate with each other to synchronize the SMEinformation and live Ad information using a variety of communicationsprotocols.

FIG. 20 is a processing flow diagram illustrating an example ofadministrative processes according to one embodiments of the invention.The processes as shown in FIG. 20 may represent the processesrepresented by GUIs as shown in FIGS. 19A-19E. Referring to FIG. 20,when an administrator such as a dispatcher successfully logs into thelive connect server at block 1001, the administrator can view one ormore pending service requests from the customers pending to bedispatched to SMEs at block 1002. The pending service requests may becentrally received at the administrator account or alternatively, thepending service requests may be returned from previously assigned SMEswho declined the requests. The administrator can communicate with acustomer (e.g., voice, text) of each of the requests at block 1003. Ifthey reach an agreement on the service contract, at block 1004, theadministrator can assign the job to one of the SMEs at block 1005. Ifthe selected SME is online, the administrator sends the user informationof the customer to the selected SME at block 1006 and a confirmation isreceived at block 1007. If the selected SME is not online, theadministrator can try to contact the SME and set the user information ofthe customer available at block 1008 and set the status of the SME tounavailable at block 1009.

According to some embodiments, the techniques described above can beutilized in a variety of scenarios. For example, in one scenario, avisitor decides to research a jewelry company that can perform thecustom creation of a ring. The visitor is not at home and decides toleverage a mobile device to start the research. A search portal systemanalyzes the visitor's search requests and provides optimized/refinedresults to the visitor via the mobile device. The visitor, whileconducting the search, is presented with a specialized Ad that presentsthe types of services the visitor is looking for. The visitor clicks ona “Live Connect” button of the Ad.

In response, a live connect Ad system performs a query to identify aspecialist slated to take personalized interactions. The system returnsthe name and location of an agent(s) who have been available, forexample, for the longest period of time (among currently availableagents). The visitor is prompted via a browser to talk directly to theavailable agent (e.g. represented via a name). Optionally, if thevisitor selects “no” via the browser when prompted with the named agent,the visitor may be directed to generic advertisement related to “generaljewelry” skill (e.g. without live connect features). Alternatively, ifthe visitor selects nothing via the browser when prompted, the visitormay also be directed to generic advertisement. Other interactions may bepossible.

If the visitor selects “yes” via the browser when prompted, the visitorwill be sent to the named specialist (or agent). The visitor may beprompted to enter a number to be contacted at (if none available). Thesystem receives the information entered by the visitor and updatessession record and processes the requests associated with theinformation entered.

For example, the system may send a live connect connection notificationto the selected specialist in response to receiving the information fromthe visitor. As the specialist receives the notification, a screen popup may be presented with the visitor data (if available) and results ofan interview (e.g. collected visitor data, phone, etc.). The specialistmay accept the notification and is placed into an “unavailable” statefor any new requests from a different visitor. The system may call thevisitor on the number provided to connect the visitor with thespecialist.

The visitor and the specialist may work through steps to complete thevisitor requests. The visitor or the specialist may disconnect from thecall. The specialist may direct the system to perform operations forwrapping up interactions between the visitor and the specialist.Subsequently, the system may update records on interactions between thevisitor and the specialist and closes the case.

In another scenario, a visitor may decide to research a jewelry companythat can perform the custom creation of a ring. The visitor is not athome and decides to leverage a mobile device to start the research. Asearch portal system may analyze the visitor's search requests toprovide optimized and/or refined results. The visitor, while conductingthe search, may be presented (e.g. via the mobile device) with aspecialized Ad that indicates the types of services the visitor islooking for. The visitor clicks on a “Live Connect” button included inthe Ad.

The live connect Ad system (or the system) may collect the visitor'sgeo-location (if allowed by visitor) and other information provided. Abusiness rule engine in the live connect Ad system may apply businessrules triggered by the visitor's Ad selection (e.g. via the clicks) andrequire pushing an interview on the visitor for more detailedinformation to get to the exact specialist to service the visitor (basedon an Ad campaign associated with the selected Ad)

In response, the visitor may be presented with user interfaces for aninterview via a mobile browser. The visitor may complete the interviewto submit additional information to the system. The system may processinformation received via the interview to identify the exact specialistfor the visitor. For example, the system performs a query to identifyspecialists slated to take personalized interactions. The system canlocate one or more specialists who are present and available. The systemmay return the name and location of a specialist(s) who have beenavailable for the longest time period. The visitor is prompted via thebrowser to talk directly to the name specialist returned by the system.If the visitor selects “no” on the browser when prompted, the visitormay be prompted by the system to request a callback for a differentday/time. If the visitor selects “yes” on the browser when prompted,information of the visitor may be sent to the named specialist for liveconnections. Other operations in response to these interactions may bepossible.

Subsequent to the selection of “yes”, the visitor is prompted to enter anumber to be contacted at (if none available from visitor data). Onreceiving the number or other information from the visitor, the systemmay update session record and process requests from the visitor. Forexample, the system may reserve a specialist and send a notification toa device of the specialist. On receiving the notification, the device ofthe specialist may present a screen pop up indicating the visitor data(if available) and results of the interview (if available).

The specialist may accept the notification and is placed into an“unavailable” state for any new requests from a different visitor. Thesystem can call (e.g. phone call or message push) the visitor on thenumber provided and establish live connections between the visitor andthe specialist. The visitor and the specialist may work through steps tocomplete visitor requested services.

The visitor (or specialist) may disconnect from the live connections(e.g. a phone call). The specialist may direct the system to performoperations for wrapping up interactions between the visitor and thespecialist. Subsequently, the system may update records on interactionsbetween the visitor and the specialist and closes the case.

In another scenario, a visitor decides to research a landscaping companythat can perform custom landscaping designs. The visitor is at home anddecides to leverage a mobile device (or a desktop device) to start theirresearch. A search portal system analyzes the visitor's search requestsand provides optimized/refined results to the visitor via the mobiledevice. The visitor, while conducting the search, is presented with aspecialized Ad that presents the types of services the visitor islooking for. The visitor clicks on a “Live Connect” button of the Ad.

The live connect Ad system (or the system) may collect the visitor'sgeo-location (if allowed by visitor) and other information provided. Abusiness rule engine in the live connect Ad system may apply businessrules triggered by the visitor's Ad selection (e.g. via the clicks) andrequire pushing an interview on the visitor for more detailedinformation to get to the exact specialist to service the visitor (basedon an Ad campaign associated with the selected Ad)

In response, the visitor may be presented with user interfaces for aninterview via a mobile browser. The visitor may complete the interviewto submit additional information to the system. Exemplary informationsolicited via the interview may include a contact number (e.g. phonenumber), visitor (or customer) name, address of location where work isto be performed, access to location (open, locked, etc.), security orsafety settings for accessing to the location (e.g. dogs to be awareof), budget for work to be performed, and/or other applicableinformation.

The system may process information received via the interview toidentify the exact specialist for the visitor. For example, the systemperforms a query to identify specialists slated to take personalizedinteractions. The system can locate one or more specialists who arepresent and available. The system may return the name and location of aspecialist(s) who have been available for the longest time period orbased on other applicable analysis or selection criteria. The visitor isprompted via the browser to talk directly to the named specialistreturned by the system. The visitor may select “yes” on the browser whenprompted.

In response, the system may reserve the specialist and send thespecialist a notification. On receiving the notification, the specialistmay be presented with a screen pop up including data related to thevisitor, such as the visitor (or customer) name and the budget for thework to be performed. The system can call (e.g. phone call or messagepush) the visitor on the number provided and establish live connectionsbetween the visitor and the specialist. The visitor and the specialistmay work through initial talks and decide that they need to meet at theresidence.

The specialist may request that the visitor take a photo of thelandscape area and submit to the specialist. The visitor may then take aphoto to be submitted. The specialist may receive the photo as a part ofthe custom (or visitor) data via a mobile application. The visitor mayclick an “accept” or “approve” button via a mobile browser to allow thespecialist to see the additional data (address, access, pets, etc.)collected from the visitor.

The system may identify that the visitor is 5 minutes away from the joblocation and the specialist may be 20 minutes away from the job location(e.g. based on geo location information tracked). The system may performscheduling operations to provide both the visitor and the specialistwith a note indicating that a meeting time of 30 minutes out isrecommended. Accordingly, the visitor may accept the recommended timevia the mobile browser. The visitor may also issue permission via themobile browser to allow the specialist to use GPS (global positionsystem) information for navigation.

The specialist accepts from the mobile app the recommended time. Thespecialist changes job state (via the system) to “in progress” keepingthe specialist “unavailable” from receiving a new notification from anAd click by a new visitor (if no specialist available, Ad is not shownvia search by visitors). The system creates a dynamic geo-fence at theresidence (e.g. the job location) of the visitor for notification uponarrival of the specialist. The specialist may be prompted to load GPSapplication to navigate to the residence. Either the visitor or thespecialist may disconnect from the live communication (e.g. a phonecall).

On arrival of the specialist at the job location, the system canidentify or detect that the specialist has reached the residence basedon the crossing of the geo-fence placed around the residence. The systemmay send the visitor a notification (e.g. via a web browser app, SMS orother applicable messaging services) related to the specialist, such ascredentials and a photo. The specialist and the visitor meet at theresidence door and proceed to the back yard where the visitor would liketo have the expected work done. The specialist proceeds to perform thework. When the work is completed, the specialist may initiate wrap upoperations of the interactions between the visitor and the specialist.

For example, the system may update records on interactions. The visitormay be prompted by an application (e.g. via embedded code delivered by amobile browser) to post comments to a social network about theirexperience with the specialist/business. The visitor is very happy withexperience and posts comments to Facebook™, Twitter™, and/or othersocial network sites. The specialist may set the job state of the workto “complete” (based on the business taxonomy defined in the adcampaign) which makes them available for a new notification for anothervisitor ad click.

The system may perform follow on actions. For example, the system cansend notification to the visitor with a thank you note from thespecialist/business. The system may order and deliver quotes to thevisitor for additional work. The system can create a case to kick offadditional work to be done. Alternatively or additionally, the systemmay perform scheduling operations to create a timed plan for thework/order.

In a further scenario, a visitor decides to see what are being played atlocal theaters. The visitor is mobile using a mobile device for thesearch. A search portal system analyzes the visitor's search requestsand provides optimized/refined results to the visitor via the mobiledevice. The visitor, while conducting the search, is presented with a“live connect” Ad related to the search via an Ad system integrated witha live connect Ad system (e.g. the system) providing the “live connect”Ad.

The visitor wanting to see the play clicks on the “live connect” Ad. Inresponse, the system performs a query to identify a box officespecialist present and available to take an interaction with thevisitor. The system locates a specialist who is present and available.The system may return the name of the specialist who has been availablelongest or meets some analysis criteria (e.g. including geo locationmatching).

The visitor may be prompted via the mobile browser to talk directly tothe available specialist (e.g. indicated by name). The visitor selects“yes” button via the mobile browser when prompted to proceed. Thevisitor may be further prompted to enter a number (e.g. phone number orother applicable contact information) to be contacted at (if noneavailable from visitor data).

On receiving the information provided by the visitor, the system updatessession records and processes the visitor's requests. The system canreserve a specialist and send a notification is sent to the specialist.A screen pop up with the visitor's data (if available) is presented tothe specialist when the notification from the system is received. Thesystem may initiate a call to the visitor based on the number providedto establish a live connection with the specialist.

The visitor and the specialist work through the ticket sale for playover the live connection. The system creates a dynamic geo-fence at theplays venue (or the theater). The visitor (or specialist) disconnectsfrom the call. The visitor heads to the theater for the show.

Once the visitor is physically close to the theater, the system detectstriggering of the geo-fence by the visitor's geo-location which has beentracked or monitored. The system can generate geo events based on thetriggering of the geo-fence. The geo events may be forwarded to thetheater's ticketing system to update inventory status of the tickets forthe play.

For example, the theater is updated with information about the visitor'sarrival and flags that the seat will be occupied. The theater can trackall sales and visitor arrivals such that if the visitors are not presentwithin a specific time close to show time of the play, the theatre canupdate the Ad to increase the discount in order to sell the seat for ahigher yield by show.

After the play ends, the visitor is prompted by a client application(e.g. based on embedded code delivered via a mobile browser) to postcomments to a social network about the play and their experience withthe theater's ad service. The visitor is very happy with experience andposts comments to Facebook™, Twitter™, and/or other social networksites.

In some embodiments, a visitor selects a live connect Ad directed to anamed specialist. Data analysis may be performed to identify a bestroute to provide requested service to the visitor. Business rules may beleveraged for soliciting additional data entered or volunteered by thevisitor. The data analysis may be based on various data including geolocations of the visitor and available specialists. Pre-qualificationinformation may be provided by the visitor via an interview mechanism,for example, to determine whether or which specialists are available toprovide requested services.

Immediate live message communication (e.g. based on short messagingservice) or live voice calls may be established via the visitor'sselection. Multiple factors may be included in selecting whichspecialist and/or which route for providing the service. The factors mayinclude current geo locations of the visitor and available specialists,business rules configured for specialist selection, applicable schedulesprovided by the visitor for a face to face meeting with the specialists,and/or other applicable criteria. Directions may be automaticallyprovided in real time for the authorized (or selected) specialist totravel for scheduled meeting with the visitor for providing therequested service. For example, geo-fencing capability may be enabled(e.g. via business rules) for visitor notifications triggered by arrivalof the selected specialist near the job location. Specialist specificinformation may be pushed to the visitor upon arrival at the visitorlocation. Interfaces for a real-time social feedback may be presented tothe visitor via a live connected ad event regarding the specialist andbusiness providing the requested service to the visitor.

As described above, a live connect server may be integrated with orcommunicatively coupled to another server representing a support centerto utilize the existing or advanced resources or infrastructure. FIG. 21is a block diagram illustrating a system for providing support servicesto products according to one embodiment of the invention. System 1100can be implemented with a live connect server described above. Referringto FIG. 21, system 1100 includes a mobile device 1101 of a user,customer, or individual communicatively coupled to service center 1102over a network. The network may be any kind of networks, such as a widearea network (WAN) (e.g., the Internet), a local area network (LAN), ora combination of both. Mobile device 1101 may be any kind of mobiledevices including, but is not limited to, a laptop, mobile phone,tablet, media player, personal digital assistant or PDA, etc.Communication connections between devices can be established either byrouting through the network or by direct initiation of calls from oneend device to another by a mobile application communicating with aserver who selects the target. For routed calls the network provides thestate of the connection and hence the call state component of agentavailability. For direct initiation, some device environments providefor notification of call state and others do not. The Apple Facetime™implementation in the iOS operating system, for example, allows videocalls to be established by API, but does not provide subsequentinformation about the call. In that case we deduce whether a call hasbeen successful and when it ends from the behavior of the operatingsystem. A timer is set when the FaceTime™ call is invoked by theapplication and examined when control is returned to the application.From the timer duration we determine whether the call was successful andwhen it ended. Note that throughout this application a mobile device isutilized as an example of a client device for the purposes ofillustration only; other devices such as a desktop or server may also beapplied herein.

Service center 1102 may be implemented in a centralized facility orserver with data processing hardware. Alternatively, service center 1102may be implemented in multiple facilities or servers in a distributedmanner (e.g., cloud-based service platforms). Service center 1102provides services to a variety of products or services from a variety ofclients or vendors. For example, service center 1102 may be a callercenter handling a variety of support call services on products orservices for a variety of goods and service providers. A client may be amanufacturer, a distributor, a retailer, a service provider or broker, apurchasing facility (e.g., Amazon™, Expedia™, or ISIS™), or acombination thereof.

In one embodiment, service center 1102 includes one or more serviceapplication programming interfaces (APIs) 1104 to communicate, over anetwork, with other systems such as mobile device 1101, client's site1117, social communities 1116, contact center 1114 including agents orexperts 1115, client backend systems 1118, manufacturer backend systems1119, eCommerce sites 1120 and other auxiliary systems (e.g., billingsystem). Service center 1102 can handle service requests from customersof multiple clients. For example, service center 1102 may handlecustomer service requests for a number of retail sales companies,sales/post sales calls for catalog sales companies, and patientfollow-up contacts for health care providers. In such a structure, theservice center may receive service requests directly from the customersor through client support management systems.

In one embodiment, service center 1102 further includes communityservice system 1105, support services system 1106, route sequencemanager 1107, and data warehouse 1109. Support services system 1106 isresponsible for handling support services requests from the users,including identifying and registering a product, creating an transactioncase context, selecting and assigning a customer representative (alsoreferred to herein as an agent, specialist, or expert) to providesupport services to the users, and managing work flows, etc. An agentmay be selected based on a skill set or expertise of the agent in askill, as well as other factors such as geographic location, of theagent. The term “agent,” “specialist,” or “expert” refers to a servicecenter personnel or a computerized application, in some cases, thatrespond to customer requests. An agent may be locally situated at theservice center or remotely situated over a network. Throughout thisapplication, the terms of “agent,” “specialist,” and “expert” areinterchangeable terms dependent upon the circumstances. In most cases,the term of “agent” collectively refers to a customer representative, asupport agent, a support specialist, a support expert, or a combinationthereof, which may be a service center personnel and/or a computerizedapplication.

FIG. 22 is a block diagram illustrating an example of support servicesystem of a service center according to one embodiment of the invention.For example, system 1200 may be implemented as a part of system 1100 ofFIG. 21. Referring to FIG. 22, system 1200 includes service APIs 1104 toallow customer 1101 to reach support center via a variety ofcommunication mediums such as chat, email, online forum, Web, video,voice, etc. Customer 1101 may initiate a contact with support center1102 via a mobile application (also referred to as a one-touchapplication) installed on the customer's mobile device as describedabove. Service APIs 1104 may include a variety of subsets of APIs suchas integrated service API 1104A, support service API 1104B, automatedservice API 1104C, and partner service API 1104D. Some or all of theseAPIs 1104A-1104D may be implemented as cloud-based service APIs, wherethe service APIs may be maintained by a third party service provider asa part of software as a server (SaaS) on a subscription basis.

In one embodiment, integrated service API 1104A may be utilized bycertain integrated service providers such as payment services 1206,dispatch services, location services, tracking and delivering services,short messaging services (SMS), social networking and blogging services(e.g., Twitter™), and customer relationship management (CRM) services(e.g., Salesforce™), etc. Automated service API 1104C may be utilized byAI Artificial Intelligence services, BOT services automated services(like roBOT) that mimic the actions or activity of a human processes oractivities making the user think they are talking to a live person,frequently-asked question (FAQ) services 1207, survey services,eLearning services, etc. Partner service API 1104D may be utilized bycertain partner entities of the support center such as social knowledge1208, multi-channel communication system 1209, and social CRM (e.g.,Lithium™) etc.

In one embodiment, support service API 1104B can be utilized by customer1101 to reach the support center. Support service API 1104B may beutilized, for example, via a one-touch application launched from amobile device, to register a user, register a product, accessknowledgebase (e.g., KBs 1113A-1113B), and obtain a support service froman agent, AI, BOT service, etc. Initially, when a customer downloads andinstalls a one-touch application on its mobile device, the customer canaccess support center 1102 via support service API 1104B to create auser account, which may be performed by registration module 1201.Subsequently, the customer may also log into the account via supportservice API 1104B, which may be authenticated by security module 1203,to register a product and/or to retrieve a list of registered one ormore products that have been registered with support center, usingcertain techniques described above.

When there is a need to contact support center 1102 on a product, thecustomer can activate the one-touch application from its mobile deviceor press a one-touch button from a Web site, which will access and loginto support center 1102 via support service API 1104B, where thecustomer and/or the mobile device can be authenticated by securitymodule 1203. In addition, case management module 1205 is configured tocreate a unique case ID that uniquely identifies the instant supportcase. The case ID may be created based on a combination of at least someof the product identifiers (e.g., serial number, barcode, quick response(QR) code, high capacity color barcode (HCCB) code, receipt transactionID), client information (e.g., retailer ID, manufacturer product ID),customer information (e.g., personal information, username, password,mobile device ID), and other information (e.g., time, date).

In one embodiment, touch plan engine 1202 is configured to create atouch plan which is identified and tracked by the case ID. The touchplan may be created according to one or more business rules or templatesof the client. The touch plan represents a roadmap, an outline, atracking record, or case context for the instant support case. The touchplan may also include or reference to other aiding information, such as,product information, product intelligence information, customer historydata, client information, and manufacturer information, etc., which maybe retrieved and compiled from various informational sources such ascustomer database 1112, client database 1111, product database 1110,knowledgebase 1113A-1113B, client and/or manufacturer backend systems,etc. The touch plan is then forwarded to an agent that has been assignedto the instant case to allow the agent to have all the necessaryinformation to enable the agent to provide the best customer experience.The agent may be assigned based on a variety of factors, such as, skillset, expertise, demographic location, language, prior customerrelationship, etc.

Data warehouse 1109 includes, but is not limited to, self-support KB1113B, internal support KB 1113A, client database (DB) 1111, productdatabase 1110, and customer database 1112. Internal support KB 1113A maystore any support information or communications between an agent and acustomer. Self-support KB 1113B contains published information extractedfrom other informational sources, such as internal support KB 1113A andother systems (e.g., client backend systems and manufacturer backendsystems). Self-support KB 1113B allows a customer to browse in anattempt to find a solution for the customer's problem, hopefully withouthaving to contact a live support agent. Client database 1111 may storeany client related information, including a client profile for eachclient supported by support center 1102. For example, client database1111 may store client's preference of communication channels to beutilized between a customer and an agent. Client database 1111 may alsocontain membership information of the customers.

Product information store 1110 may store any user manual or technicalmanual of products. Product detailed information may further includecomplementary products and services, availability, etc. Such informationmay be drawn from external systems such as client's backend systemsand/or manufacturer's backend systems. Customer DB 1112 may store anycustomer related information such as personal information (e.g., name,address, phone numbers, sex, age), security credential, device ID of itsmobile device, etc. Customer DB 1112 may store any product that has beenregistered by a customer. Customer DB 1112 may further store informationregarding any interaction between a customer and an agent of previoussupport sessions, such as topics, detailed discussions, time of thediscussions, contact mechanisms used, reasons of the support, productsor services involved in the discussions, last agent or expert thecustomer interacted with, etc.

Other databases may also be included and utilized. For example, an agentor expert database may be maintained for the purpose of selecting anappropriate agent or expert in response to a support service from acustomer. An agent and expert information database may include a profilefor each agent or expert, respectively, that includes individual agentor expert identifier, individual name, address, communication deviceinformation, personal information (e.g., age, sex, hobbies, physicalcondition, spoken languages, ethnicity, geographic area of expertise,etc.), individual skills and/or areas of expertise. The agent/expertdatabase may further include day(s) and time(s) during which and/orareas in which the agent/expert may be contacted to service customercontacts and/or a number of times over a selected period in which theagent/expert may be contacted to service customer contacts (e.g.,similar to presence information).

In addition, a service statistics database may also be maintained. Aservice statistics database may represent any database that stores datarelated to the operation and management of the support center system1102. Data such as the number of customers in queue at a certain dateand time, the duration of support contact in queue, the rate of contactabandonment, and the use of communication resources are stored in thestatistics database. Note that the databases and data stores are shownand described for the purposes of illustration only. These databases anddata stores can be implemented or configured in a variety ofconfigurations, which may be implemented locally or remotely over anetwork. Note that some databases or data stores may be implemented as asingle database or store or multiple databases or stores.

In one embodiment, registration module 1201 is responsible forregistering a customer and/or a product of a customer, where thecustomer's personal information or preferences may be stored in acustomer profile store as part of customer DB 1112, while the registeredproduct information may be stored in customer DB 1112. For example, whena customer installs a one-touch application on its mobile device, thecustomer typically performs an initial login to set up a user account,including a username and/or password, as well as customer's preferences(e.g., communication channel preferences). In one embodiment,registration module 1201 can also be used to assist in registering auser for other accounts such as a loyalty account across one or moreloyalty programs, a rewards program, etc. This information may be storedin customer DB 1112. In addition, a unique device ID such as a MACaddress or IMSI code may be captured and stored in customer DB 1112. Asa result, when the customer subsequently launches the one-touchapplication, the customer can be automatically authenticated by securitymodule 1203 based on this information without requiring the customer toprovide the same information again.

According to one embodiment, when a one-touch application is activatedor launched from a mobile device by a user, the one-touch application isconfigured to communicate with service API 1104. Service API 1104invokes security module 1203 to authenticate the user based on theinformation (e.g., MAC or IMSI) transmitted from the one-touchapplication without requiring the user to specifically provide userinformation.

Once the user has been authenticated, according to one embodiment,service API 1104 transmits a personalized page having a list of one ormore products from a customer asset store (not shown) that have beenregistered to the user. The list of the registered products may bedisplayed on a display of the mobile device, where each product isassociated with one or more communication channels that are availablefor the user to contact an agent of the support center. In oneembodiment, the availability of the communication channels is determinedbased on the user preference obtained from customer DB 1112 and theclient/vendor preference from client database 1111 at that point intime. Such user preference and client/vendor preference may beconfigured in a user profile and client/vendor profile, respectively,which may be maintained by the support center.

In response to a selection of one or more of the available communicationchannels received at the service API, according to one embodiment, aunique case identification (ID) is instantly created by case managementmodule 1205 to uniquely represent a current instant of the support case.In addition, a touch plan is created by touch plan engine 1202 andtracked by the unique case ID, where the touch plan represents a roadmapor outline of the corresponding support case activities to be performedthroughout the life of the touch plan. The touch plan is updatedregarding all activity of the user and is forwarded to an agent assignedto the current case and a communication session is established betweenthe assigned agent and the user via the selected communication channel.Throughout the session the touch plan is updated on all activity betweenthe user, agent and their respective applications.

An agent may be selected based on a variety of considerations, such as askill set or expertise of the agent, as well as whether the agent hasprevious experience with the same customer. The touch plan may includeone or more references linked with all the information related to thecurrent instant support service, such as related product information,client information, customer information, and support history with thecustomer, etc., such that the agent can provide the best possibleservices to the customer. The touch plan may further include suggestionor prediction of products or services that the agent can provide thecustomer an alternative solution. The suggestion or prediction may begenerated by a persuasive engine (not shown) based on the productinformation and the customer's interactive history, etc. The interactionbetween the user and the agent is logged by a logging module (not shown)and tracked based on the touch plan and the unique case ID, which may bestored in an interaction history database, for example, for subsequentanalysis by an analysis module.

Processing logic associated with the touch plan (e.g., touch planengine, case management module, or some other logic) also monitors forpositive and negative activities from the user, the agent and respectiveapplications. If a negative event is occurring the processing logic canperform adjustments according to the touch plan in knowledge provided,agent scripting spoken to the user and many others in a manner such toturn the interaction positive (e.g., adapt to changing conditions andcircumstances). If the activity is positive the processing logic canprovide an additional activity in and around product or service upsell,cross sell, upgrades, and product sales, etc. The positive and negativeactivity monitoring and adjustments are not limited to a user and agent,they can support any form of interaction even long running interactionsthat exceed the user activity for any period of time.

In some situations, according to one embodiment of the invention, thetouch plan may include information that identifies a relationshipbetween two products or services that have been purchased via a client(e.g., purchasing house). When a first product/service changes, thesupport center may determine that a second product/service may need tochange as well based on the touch plan. Accordingly, a proactive servicemodule (not shown) is configured to proactively notify the userregarding the possible change of the second product/service and offerssupport services for the second product/service, without requiring theuser to initiate a support call. A suggestion or offer can be made tothe customer by a persuasive engine based on the information obtainedfrom databases 1111-1113 of data warehouse 1109.

According to one embodiment, prior to contacting an agent, a list ofsupport options may be presented to the user, including a link to apublication forum that may contain one or more solutions to a problemassociated with the user. Such solutions may be generated by apublication module (not shown) by extracting certain information fromknowledgebase from a variety of informational sources, such as, forexample, internal support KB 1113A, client/vendor KB (e.g., clientdatabase 1111 and client backend system), manufacturer KB (e.g., productdatabase 1110 and manufacturer backend system), online community KB,and/or customer interactive history KB, etc. As a result, a user mayfind a solution from the publication forum and does not need to contactan agent of the support center, which in turn may lower the cost for theclient and/or the customer. This is also referred to as a call avoidancefeature. Certain information from data warehouse 1109 may be queried andreported by a reporting module.

Note that components or modules shown in FIG. 22 are described for thepurpose of illustration only; more or fewer components or modules mayalso be implemented. For example, a customer satisfaction system (CSAT)may also be implemented within support center 1102. A CSAT systemprovides a feedback form to a customer, through a variety ofcommunication channels at the completion of a request or a query made bythe customer. The feedback form filled out and provided by customers isstored, reviewed, and analyzed by the CSAT system. All feedback formsstored in the CSAT system are used as a tool to conduct a customerservice related survey. The feedback forms are, further used to enhancethe service provided by support center 1102.

Referring back to FIG. 21, in one embodiment, community service system1105 is responsible for communicating with social communities 1116 viaan API, for example, to post a message received from a user and to routethe responses received from social communities 1116 back to the user.Service center 1102 further includes other components such as a postmarket service system 1122, which is responsible for handling postmarket activities associated with the registered products, includingselling a registered product on eCommerce sites 1120 and arranging adisposal facility to dispose or recycle the product, etc.

According to one embodiment, in addition to registering a product withthe service center, a user can also register, for example, through theapplication running within a mobile device, one or more socialcommunities and/or one or more eCommerce sites by storing the necessarycredentials (e.g., usernames and passwords) of the servers hosting thesocial communities and eCommerce sites in a database (e.g., userdatabase) of the service center, where the database is associated with auser the mobile device. Subsequently, the user can transmit a salesrequest to sell or dispose a registered product by specifying one ormore of the eCommerce sites.

In response to the sales request, post market service system 1122 ofservice center 1102 is configured to retrieve the necessary credentialsfor the specified one or more eCommerce sites and arrange the specifiedeCommerce sites for selling the product together with the associatedcredentials to allow the eCommerce sites to authenticate the user forthe purpose of selling the product, such that the user does not have toprovide the necessary credentials at the point in time of the salesrequest and the user does not have to provide detailed information ofthe product to be posted on the eCommerce sites describing the productto be sold. A single sales request received from the mobile device canspecify multiple eCommerce sites. The service center can also arrange adisposal facility to dispose (e.g., recycle) a registered productwithout having a user to specifically contact the disposal facility.

Some portions of the preceding detailed descriptions have been presentedin terms of algorithms and symbolic representations of operations ondata bits within a computer memory. These algorithmic descriptions andrepresentations are the ways used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the above discussion, itis appreciated that throughout the description, discussions utilizingterms such as those set forth in the claims below, refer to the actionand processes of a computer system, or similar electronic computingdevice, that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

Embodiments of the invention also relate to an apparatus for performingthe operations herein. Such a computer program is stored in anon-transitory computer readable medium. A machine-readable mediumincludes any mechanism for storing information in a form readable by amachine (e.g., a computer). For example, a machine-readable (e.g.,computer-readable) medium includes a machine (e.g., a computer) readablestorage medium (e.g., read only memory (“ROM”), random access memory(“RAM”), magnetic disk storage media, optical storage media, flashmemory devices).

The processes or methods depicted in the preceding figures may beperformed by processing logic that comprises hardware (e.g. circuitry,dedicated logic, etc.), software (e.g., embodied on a non-transitorycomputer readable medium), or a combination of both. Although theprocesses or methods are described above in terms of some sequentialoperations, it should be appreciated that some of the operationsdescribed may be performed in a different order. Moreover, someoperations may be performed in parallel rather than sequentially.

Embodiments of the present invention are not described with reference toany particular programming language. It will be appreciated that avariety of programming languages may be used to implement the teachingsof embodiments of the invention as described herein.

In the foregoing specification, embodiments of the invention have beendescribed with reference to specific exemplary embodiments thereof. Itwill be evident that various modifications may be made thereto withoutdeparting from the broader spirit and scope of the invention as setforth in the following claims. The specification and drawings are,accordingly, to be regarded in an illustrative sense rather than arestrictive sense.

What is claimed is:
 1. A computer-implemented method for routingmessages amongst multiple parties associated with a media presentation,the method comprising: receiving, at a first server from a second serverover a network, a first request of a first user for communicating withan agent concerning a content item of a media presentation presented tothe first user, wherein the first request includes a content identifieridentifying the content item presented by the second server; in responseto the first request, identifying from a client database one or moreagents that are associated with the content identifier, the clientdatabase storing content identifiers identifying a plurality of mediapresentations, wherein the media presentations are owned by a pluralityof media presentation owners as clients to the first server; determininga status of each of the identified agents from an agent database,including determining whether each of the identified agents is availableto communicate with the first user to discuss the content item at apoint in time, wherein the agent database stores agent information of aplurality of agents; transmitting a list of one or more agentidentifiers to the second server, the agent identifiers identifying oneor more agents that are available at real time to discuss with the firstuser concerning the content item, including a geographic location ofeach of the identified agents to be presented to the first user by thesecond server, wherein the one or more agents of the list are associatedwith an owner of the content item; receiving at the first server asecond request from a first user device of the first user, the secondrequest including an agent identifier identifying a first agent selectedby the first user from the list and contact information of the firstuser; and in response to the second request, transmitting a firstmessage to a first agent device of the first agent, the first messageincluding the content identifier identifying the content item and thecontact information of the first user, wherein the first agent is toestablish a live communication session with the first user using thecontact information of the first user for discussing the content item.2. The method of claim 1, wherein the client database comprises aplurality of entries, each corresponding to one of the plurality ofclients associated with the media presentations presented by the secondserver, and wherein each entry contains one or more agent identifiersidentifying one or more agents in one of one or more groups, each groupbeing associated with one of the plurality of media presentationspresented by the second server.
 3. The method of claim 2, wherein groupsof agents are assigned to different media presentations by the owners ofthe media presentations via a user interface maintained by the firstserver and stored in the client database, prior to receiving the firstrequest.
 4. The method of claim 2, wherein identifying from a clientdatabase one or more agents that are associated with the content itemcomprises: extracting the content identifier from the first request,wherein the content identifier includes a resource link presented withthe content item at the second server, wherein the resource link whenactivated causes the first request to be transmitted from the secondserver to the first server; performing a first lookup operation in theclient database based on the content identifier to locate a first entryhaving a first field matching the content identifier; and retrieving theagent identifiers from a second field of the first entry, the agentidentifiers identifying one or more agents that are associated with acontent item identified by the first field.
 5. The method of claim 2,wherein determining a status of each of the identified agents comprises:for each of the agent identifiers, iteratively performing a secondlookup operation in an agent database, including locating a second entryhaving a third field that matches the agent identifier; and determiningin a fourth field of the second entry a status of an agent identified bythe agent identifier, including whether the agent is available toconduct a live communication session with the first user, wherein thestatus is one of available status and unavailable status.
 6. The methodof claim 5, further comprising: receiving a second message from thefirst agent device of the first agent in response to the first message,indicating that the first agent agrees to contact the first user; and inresponse to the second message, automatically setting the status of thefirst agent to the unavailable status in an entry of the agent databasecorresponding to the first agent.
 7. The method of claim 6, furthercomprising: receiving a first signal indicating the first agent istraveling to a premises of the first user; in response to the firstsignal, dynamically configuring a geo-fence representing a predeterminedgeographical proximity with respect to the geographical location of thefirst user; periodically tracking a geographical location of the firstagent device of the first agent; receiving a second signal indicatingthat the first agent device is within the geo-fence; in response to thesecond signal, transmitting identifying information of the first agentto the first user device of the first user, indicating that the firstagent is about arriving at the premises.
 8. The method of claim 5,further comprising: in response to the second request, determining fromthe agent database whether the first agent is still available at thepoint in time of receiving the second request; and in response todetermining that the first agent is unavailable, transmitting the firstmessage to a second agent device of a second agent to allow the secondagent to establish the live communication session with the first user,wherein the second agent has been configured as a default agent if noneof the agents in the list is available.
 9. The method of claim 5,further comprising: in response to the second request, determining fromthe agent database whether the first agent is still available at thepoint in time of receiving the second request; in response todetermining that the first agent is unavailable, transmitting the firstmessage to a third agent, including information identifying remainingagents in the list that are available based on their statuses from theagent database and geographic locations of the remaining agents, toallow the third agent to select one of the remaining agents; and inresponse to a third message received from the third agent selecting afourth agent from the remaining agents, transmitting the first messageto a fourth agent device of the fourth agent to allow the fourth agentto contact the first user.
 10. The method of claim 5, furthercomprising: receiving a third message from the second agent device ofthe second agent in response to the first message, indicating that thesecond agent has denied to contact the first user; in response to thethird message, transmitting the first message to a third agent device ofa third agent to allow the third agent to contact the first user,wherein the third agent has been configured as a default agent if noneof the agents in the list is available; and automatically setting astatus of the second agent to unavailable in an entry of the agentdatabase corresponding to the second agent.
 11. The method of claim 1,wherein the first request further comprises a first geographic locationof the first user, and wherein the agent identifiers transmitted to thesecond server are selected based on geographic locations of the agentsidentified by the agent identifiers in view of the first geographiclocation of the first user.
 12. The method of claim 11, whereintransmitting a list of one or more agent identifiers to the secondserver comprises: for each of the agent identifiers, obtaining via alocation service a longitude and a latitude of a mobile device of anagent identified by the agent identifier; and transmitting the longitudeand a latitude of the mobile device to the second server to be presentedas a part of a map with respect to the first geographic location of thefirst user.
 13. A non-transitory machine-readable medium havinginstructions stored therein, which when executed by a processor, causethe processor to perform operations for routing messages amongstmultiple parties associated with a media presentation, the operationscomprising: receiving, at a first server from a second server over anetwork, a first request of a first user for communicating with an agentconcerning a content item of a media presentation presented to the firstuser, wherein the first request includes a content identifieridentifying the content item presented by the second server; in responseto the first request, identifying from a client database one or moreagents that are associated with the content identifier, the clientdatabase storing content identifiers identifying a plurality of mediapresentations, wherein the media presentations are owned by a pluralityof media presentation owners as clients to the first server; determininga status of each of the identified agents from an agent database,including determining whether each of the identified agents is availableto communicate with the first user to discuss the content item at apoint in time, wherein the agent database stores agent information of aplurality of agents; transmitting a list of one or more agentidentifiers to the second server, the agent identifiers identifying oneor more agents that are available at real time to discuss with the firstuser concerning the content item, including a geographic location ofeach of the identified agents to be presented to the first user by thesecond server, wherein the one or more agents of the list are associatedwith an owner of the content item; receiving at the first server asecond request from a first user device of the first user, the secondrequest including an agent identifier identifying a first agent selectedby the first user from the list and contact information of the firstuser; and in response to the second request, transmitting a firstmessage to a first agent device of the first agent, the first messageincluding the content identifier identifying the content item and thecontact information of the first user, wherein the first agent is toestablish a live communication session with the first user using thecontact information of the first user for discussing the content item.14. The non-transitory machine-readable medium of claim 13, wherein theclient database comprises a plurality of entries, each corresponding toone of the plurality of clients associated with the media presentationspresented by the second server, and wherein each entry contains one ormore agent identifiers identifying one or more agents in one of one ormore groups, each group being associated with one of the plurality ofmedia presentations presented by the second server.
 15. Thenon-transitory machine-readable medium of claim 14, wherein groups ofagents are assigned to different media presentations by the owners ofthe media presentations via a user interface maintained by the firstserver and stored in the client database, prior to receiving the firstrequest.
 16. The non-transitory machine-readable medium of claim 14,wherein identifying from a client database one or more agents that areassociated with the content item comprises: extracting the contentidentifier from the first request, wherein the content identifierincludes a resource link presented with the content item at the secondserver, wherein the resource link when activated causes the firstrequest to be transmitted from the second server to the first server;performing a first lookup operation in the client database based on thecontent identifier to locate a first entry having a first field matchingthe content identifier; and retrieving the agent identifiers from asecond field of the first entry, the agent identifiers identifying oneor more agents that are associated with a content item identified by thefirst field.
 17. The non-transitory machine-readable medium of claim 14,wherein determining a status of each of the identified agents comprises:for each of the agent identifiers, iteratively performing a secondlookup operation in an agent database, including locating a second entryhaving a third field that matches the agent identifier; and determiningin a fourth field of the second entry a status of an agent identified bythe agent identifier, including whether the agent is available toconduct a live communication session with the first user, wherein thestatus is one of available status and unavailable status.
 18. Thenon-transitory machine-readable medium of claim 17, wherein theoperations further comprise: receiving a second message from the firstagent device of the first agent in response to the first message,indicating that the first agent agrees to contact the first user; and inresponse to the second message, automatically setting the status of thefirst agent to the unavailable status in an entry of the agent databasecorresponding to the first agent.
 19. The non-transitorymachine-readable medium of claim 8, wherein the operations furthercomprise: receiving a first signal indicating the first agent istraveling to a premises of the first user; in response to the firstsignal, dynamically configuring a geo-fence representing a predeterminedgeographical proximity with respect to the geographical location of thefirst user; periodically tracking a geographical location of the firstagent device of the first agent; receiving a second signal indicatingthat the first agent device is within the geo-fence; in response to thesecond signal, transmitting identifying information of the first agentto the first user device of the first user, indicating that the firstagent is about arriving at the premises.
 20. The non-transitorymachine-readable medium of claim 17, wherein the operations furthercomprise: in response to the second request, determining from the agentdatabase whether the first agent is still available at the point in timeof receiving the second request; and in response to determining that thefirst agent is unavailable, transmitting the first message to a secondagent device of a second agent to allow the second agent to establishthe live communication session with the first user, wherein the secondagent has been configured as a default agent if none of the agents inthe list is available.
 21. The non-transitory machine-readable medium ofclaim 17, wherein the operations further comprise: in response to thesecond request, determining from the agent database whether the firstagent is still available at the point in time of receiving the secondrequest; in response to determining that the first agent is unavailable,transmitting the first message to a third agent, including informationidentifying remaining agents in the list that are available based ontheir statuses from the agent database and geographic locations of theremaining agents, to allow the third agent to select one of theremaining agents; and in response to a third message received from thethird agent selecting a fourth agent from the remaining agents,transmitting the first message to a fourth agent device of the fourthagent to allow the fourth agent to contact the first user.
 22. Thenon-transitory machine-readable medium of claim 17, wherein theoperations further comprise: receiving a third message from the secondagent device of the second agent in response to the first message,indicating that the second agent has denied to contact the first user;in response to the third message, transmitting the first message to athird agent device of a third agent to allow the third agent to contactthe first user, wherein the third agent has been configured as a defaultagent if none of the agents in the list is available; and automaticallysetting a status of the second agent to unavailable in an entry of theagent database corresponding to the second agent.
 23. The non-transitorymachine-readable medium of claim 13, wherein the first request furthercomprises a first geographic location of the first user, and wherein theagent identifiers transmitted to the second server are selected based ongeographic locations of the agents identified by the agent identifiersin view of the first geographic location of the first user.
 24. Thenon-transitory machine-readable medium of claim 23, wherein transmittinga list of one or more agent identifiers to the second server comprises:for each of the agent identifiers, obtaining via a location service alongitude and a latitude of a mobile device of an agent identified bythe agent identifier; and transmitting the longitude and a latitude ofthe mobile device to the second server to be presented as a part of amap with respect to the first geographic location of the first user. 25.A system for routing messages amongst multiple parties associated with amedia presentation, the system comprising: a processor; a memory coupledto processor; a storage device to store a client database and an agentdatabase, which are loaded in the memory by the processor; anavailability module coupled to the processor and the memory to receivefrom a second server over a network, a first request of a first user forcommunicating with an agent concerning a content item of a mediapresentation presented to the first user, wherein the first requestincludes a content identifier identifying the content item presented bythe second server, in response to the first request, identify from theclient database one or more agents that are associated with the contentidentifier, the client database storing content identifiers identifyinga plurality of media presentations, wherein the media presentations areowned by a plurality of media presentation owners as clients to thefirst server, determine a status of each of the identified agents fromthe agent database, including determining whether each of the identifiedagents is available to communicate with the first user to discuss thecontent item at a point in time, wherein the agent database stores agentinformation of a plurality of agents, and transmit a list of one or moreagent identifiers to the second server, the agent identifiersidentifying one or more agents that are available at real time todiscuss with the first user concerning the content item, including ageographic location of each of the identified agents to be presented tothe first user by the second server, wherein the one or more agents ofthe list are associated with an owner of the content item; and a liveconnect module coupled to the processor and the memory to receive asecond request from a first user device of the first user, the secondrequest including an agent identifier identifying a first agent selectedby the first user from the list and contact information of the firstuser, and in response to the second request, transmit a first message toa first agent device of the first agent, the first message including thecontent identifier identifying the content item and the contactinformation of the first user, wherein the first agent is to establish alive communication session with the first user using the contactinformation of the first user for discussing the content item.
 26. Thesystem of claim 25, wherein the client database comprises a plurality ofentries, each corresponding to one of the plurality of clientsassociated with the media presentations presented by the second server,and wherein each entry contains one or more agent identifiersidentifying one or more agents in one of one or more groups, each groupbeing associated with one of the plurality of media presentationspresented by the second server.
 27. The system of claim 26, whereingroups of agents are assigned to different media presentations by theowners of the media presentations via a user interface maintained by thefirst server and stored in the client database, prior to receiving thefirst request.